
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>
20 lines
771 B
Plaintext
20 lines
771 B
Plaintext
Git v1.6.5.7 Release Notes
|
|
==========================
|
|
|
|
Fixes since v1.6.5.6
|
|
--------------------
|
|
|
|
* If a user specifies a color for a <slot> (i.e. a class of things to show
|
|
in a particular color) that is known only by newer versions of git
|
|
(e.g. "color.diff.func" was recently added for upcoming 1.6.6 release),
|
|
an older version of git should just ignore them. Instead we diagnosed
|
|
it as an error.
|
|
|
|
* With help.autocorrect set to non-zero value, the logic to guess typos
|
|
in the subcommand name misfired and ran a random nonsense command.
|
|
|
|
* If a command is run with an absolute path as a pathspec inside a bare
|
|
repository, e.g. "rev-list HEAD -- /home", the code tried to run
|
|
strlen() on NULL, which is the result of get_git_work_tree(), and
|
|
segfaulted.
|