diff options
author | Junio C Hamano <gitster@pobox.com> | 2009-12-03 14:07:32 -0800 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2009-12-03 14:07:32 -0800 |
commit | adf9628ea41bd226dc5ab38daa0bc661097a2127 (patch) | |
tree | 6bf7ed69e25636f8c5645cf575b93f021688b955 | |
parent | Merge branch 'uk/maint-shortlog-encoding' into maint (diff) | |
download | tgif-adf9628ea41bd226dc5ab38daa0bc661097a2127.tar.xz |
Prepare for 1.6.5.5
Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r-- | Documentation/RelNotes-1.6.5.5.txt | 44 |
1 files changed, 44 insertions, 0 deletions
diff --git a/Documentation/RelNotes-1.6.5.5.txt b/Documentation/RelNotes-1.6.5.5.txt new file mode 100644 index 0000000000..616e0dd0fd --- /dev/null +++ b/Documentation/RelNotes-1.6.5.5.txt @@ -0,0 +1,44 @@ +Git v1.6.5.5 Release Notes +========================== + +Fixes since v1.6.5.4 +-------------------- + + * Manual pages can be formatted with older xmlto again. + + * GREP_OPTIONS exported from user's environment could have broken + our scripted commands. + + * In configuration files, a few variables that name paths can begin with + ~/ and ~username/ and they are expanded as expected. This is not a + bugfix but 1.6.6 will have this and without backporting users cannot + easily use the same ~/.gitconfig across versions. + + * "git diff -B -M" did the same computation to hash lines of contents + twice, and held onto memory after it has used the data in it + unnecessarily before it freed. + + * "git format-patch revisions... -- path" issued an incorrect error + message that suggested to use "--" on the command line when path + does not exist in the current work tree (it is a separate matter if + it makes sense to limit format-patch with pathspecs like that + without using the --full-diff option). + + * "git grep -F -i StRiNg" did not work as expected. + + * Enumeration of available merge strategies iterated over the list of + commands in a wrong way, sometimes producing an incorrect result. + + * "git shortlog" did not honor the "encoding" header embedded in the + commit object like "git log" did. + + * Reading progress messages that come from the remote side while running + "git pull" is given precedence over reading the actual pack data to + prevent garbled progress message on the user's terminal. + + * "git rebase" got confused when the log message began with certain + strings that looked like Subject:, Date: or From: header. + +Other minor documentation updates are included. + +v1.6.5.4-47-gdda8f4b |