
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>
27 lines
969 B
Plaintext
27 lines
969 B
Plaintext
Git v1.7.6.5 Release Notes
|
|
==========================
|
|
|
|
Fixes since v1.7.6.4
|
|
--------------------
|
|
|
|
* The date parser did not accept timezone designators that lack minutes
|
|
part and also has a colon between "hh:mm".
|
|
|
|
* After fetching from a remote that has very long refname, the reporting
|
|
output could have corrupted by overrunning a static buffer.
|
|
|
|
* "git mergetool" did not use its arguments as pathspec, but as a path to
|
|
the file that may not even have any conflict.
|
|
|
|
* "git name-rev --all" tried to name all _objects_, naturally failing to
|
|
describe many blobs and trees, instead of showing only commits as
|
|
advertised in its documentation.
|
|
|
|
* "git remote rename $a $b" were not careful to match the remote name
|
|
against $a (i.e. source side of the remote nickname).
|
|
|
|
* "gitweb" used to produce a non-working link while showing the contents
|
|
of a blob, when JavaScript actions are enabled.
|
|
|
|
Also contains minor fixes and documentation updates.
|