
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>
46 lines
1.5 KiB
Plaintext
46 lines
1.5 KiB
Plaintext
GIT v1.6.2.2 Release Notes
|
|
==========================
|
|
|
|
Fixes since v1.6.2.1
|
|
--------------------
|
|
|
|
* A longstanding confusing description of what --pickaxe option of
|
|
git-diff does has been clarified in the documentation.
|
|
|
|
* "git-blame -S" did not quite work near the commits that were given
|
|
on the command line correctly.
|
|
|
|
* "git diff --pickaxe-regexp" did not count overlapping matches
|
|
correctly.
|
|
|
|
* "git diff" did not feed files in work-tree representation to external
|
|
diff and textconv.
|
|
|
|
* "git-fetch" in a repository that was not cloned from anywhere said
|
|
it cannot find 'origin', which was hard to understand for new people.
|
|
|
|
* "git-format-patch --numbered-files --stdout" did not have to die of
|
|
incompatible options; it now simply ignores --numbered-files as no files
|
|
are produced anyway.
|
|
|
|
* "git-ls-files --deleted" did not work well with GIT_DIR&GIT_WORK_TREE.
|
|
|
|
* "git-read-tree A B C..." without -m option has been broken for a long
|
|
time.
|
|
|
|
* git-send-email ignored --in-reply-to when --no-thread was given.
|
|
|
|
* 'git-submodule add' did not tolerate extra slashes and ./ in the path it
|
|
accepted from the command line; it now is more lenient.
|
|
|
|
* git-svn misbehaved when the project contained a path that began with
|
|
two dashes.
|
|
|
|
* import-zips script (in contrib) did not compute the common directory
|
|
prefix correctly.
|
|
|
|
* miscompilation of negated enum constants by old gcc (2.9) affected the
|
|
codepaths to spawn subprocesses.
|
|
|
|
Many small documentation updates are included as well.
|