
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>
33 lines
1.2 KiB
Plaintext
33 lines
1.2 KiB
Plaintext
Git v1.6.5.4 Release Notes
|
|
==========================
|
|
|
|
Fixes since v1.6.5.3
|
|
--------------------
|
|
|
|
* "git help" (without argument) used to check if you are in a directory
|
|
under git control. There was no breakage in behaviour per-se, but this
|
|
was unnecessary.
|
|
|
|
* "git prune-packed" gave progress output even when its standard error is
|
|
not connected to a terminal; this caused cron jobs that run it to
|
|
produce cruft.
|
|
|
|
* "git pack-objects --all-progress" is an option to ask progress output
|
|
from write-object phase _if_ progress output were to be produced, and
|
|
shouldn't have forced the progress output.
|
|
|
|
* "git apply -p<n> --directory=<elsewhere>" did not work well for a
|
|
non-default value of n.
|
|
|
|
* "git merge foo HEAD" was misparsed as an old-style invocation of the
|
|
command and produced a confusing error message. As it does not specify
|
|
any other branch to merge, it shouldn't be mistaken as such. We will
|
|
remove the old style "git merge <message> HEAD <commit>..." syntax in
|
|
future versions, but not in this release,
|
|
|
|
* "git merge -m <message> <branch>..." added the standard merge message
|
|
on its own after user-supplied message, which should have overridden the
|
|
standard one.
|
|
|
|
Other minor documentation updates are included.
|