
We presently use the ".txt" extension for our AsciiDoc files. While not wrong, most editors do not associate this extension with AsciiDoc, meaning that contributors don't get automatic editor functionality that could be useful, such as syntax highlighting and prose linting. It is much more common to use the ".adoc" extension for AsciiDoc files, since this helps editors automatically detect files and also allows various forges to provide rich (HTML-like) rendering. Let's do that here, renaming all of the files and updating the includes where relevant. Adjust the various build scripts and makefiles to use the new extension as well. Note that this should not result in any user-visible changes to the documentation. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
26 lines
783 B
Plaintext
26 lines
783 B
Plaintext
GIT v1.5.3.8 Release Notes
|
|
==========================
|
|
|
|
Fixes since v1.5.3.7
|
|
--------------------
|
|
|
|
* Some documentation used "email.com" as an example domain.
|
|
|
|
* git-svn fix to handle funky branch and project names going over
|
|
http/https correctly.
|
|
|
|
* git-svn fix to tone down a needlessly alarming warning message.
|
|
|
|
* git-clone did not correctly report errors while fetching over http.
|
|
|
|
* git-send-email added redundant Message-Id: header to the outgoing
|
|
e-mail when the patch text already had one.
|
|
|
|
* a read-beyond-end-of-buffer bug in configuration file updater was fixed.
|
|
|
|
* git-grep used to show the same hit repeatedly for unmerged paths.
|
|
|
|
* After amending the patch title in "git-am -i", the command did not
|
|
report the patch it applied with the updated title.
|
|
|