diff options
author | Nicolas Pitre <nico@fluxnic.net> | 2010-09-06 20:29:57 -0400 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2010-09-06 17:41:18 -0700 |
commit | 761e742d69296393804e9a942263e86ece369257 (patch) | |
tree | 024ef23b84b09f8e5b59ec28731fffea4ba2130b /Documentation/RelNotes/1.6.5.4.txt | |
parent | Merge branch 'maint' (diff) | |
download | tgif-761e742d69296393804e9a942263e86ece369257.tar.xz |
Documentation: move RelNotes into a directory of their own
There are 108 of them already. That's a bit more than one third of
all the files in the Documentation directory already, and still growing.
Signed-off-by: Nicolas Pitre <nico@fluxnic.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/RelNotes/1.6.5.4.txt')
-rw-r--r-- | Documentation/RelNotes/1.6.5.4.txt | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/Documentation/RelNotes/1.6.5.4.txt b/Documentation/RelNotes/1.6.5.4.txt new file mode 100644 index 0000000000..d3a2a3e712 --- /dev/null +++ b/Documentation/RelNotes/1.6.5.4.txt @@ -0,0 +1,32 @@ +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 crufts. + + * "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. |