1f010d6bdf
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>
45 lines
1.5 KiB
Plaintext
45 lines
1.5 KiB
Plaintext
GIT v1.5.5.1 Release Notes
|
|
==========================
|
|
|
|
Fixes since v1.5.5
|
|
------------------
|
|
|
|
* "git archive --prefix=$path/" mishandled gitattributes.
|
|
|
|
* "git fetch -v" that fetches into FETCH_HEAD did not report the summary
|
|
the same way as done for updating the tracking refs.
|
|
|
|
* "git svn" misbehaved when the configuration file customized the "git
|
|
log" output format using format.pretty.
|
|
|
|
* "git submodule status" leaked an unnecessary error message.
|
|
|
|
* "git log --date-order --topo-order" did not override the earlier
|
|
date-order with topo-order as expected.
|
|
|
|
* "git bisect good $this" did not check the validity of the revision
|
|
given properly.
|
|
|
|
* "url.<there>.insteadOf" did not work correctly.
|
|
|
|
* "git clean" ran inside subdirectory behaved as if the directory was
|
|
explicitly specified for removal by the end user from the top level.
|
|
|
|
* "git bisect" from a detached head leaked an unnecessary error message.
|
|
|
|
* "git bisect good $a $b" when $a is Ok but $b is bogus should have
|
|
atomically failed before marking $a as good.
|
|
|
|
* "git fmt-merge-msg" did not clean up leading empty lines from commit
|
|
log messages like "git log" family does.
|
|
|
|
* "git am" recorded a commit with empty Subject: line without
|
|
complaining.
|
|
|
|
* when given a commit log message whose first paragraph consists of
|
|
multiple lines, "git rebase" squashed it into a single line.
|
|
|
|
* "git remote add $bogus_name $url" did not complain properly.
|
|
|
|
Also comes with various documentation updates.
|