1GIT v1.6.0.3 Release Notes 2========================== 3 4Fixes since v1.6.0.2 5-------------------- 6 7* "git archive --format=zip" did not honor core.autocrlf while 8 --format=tar did. 9 10* Continuing "git rebase -i" was very confused when the user left modified 11 files in the working tree while resolving conflicts. 12 13* Continuing "git rebase -i" was also very confused when the user left 14 some staged changes in the index after "edit". 15 16* "git rebase -i" now honors the pre-rebase hook, just like the 17 other rebase implementations "git rebase" and "git rebase -m". 18 19* "git rebase -i" incorrectly aborted when there is no commit to replay. 20 21* Behaviour of "git diff --quiet" was inconsistent with "diff --exit-code" 22 with the output redirected to /dev/null. 23 24* "git diff --no-index" on binary files no longer outputs a bogus 25 "diff --git" header line. 26 27* "git diff" hunk header patterns with multiple elements separated by LF 28 were not used correctly. 29 30* Hunk headers in "git diff" default to using extended regular 31 expressions, fixing some of the internal patterns on non-GNU 32 platforms. 33 34* New config "diff.*.xfuncname" exposes extended regular expressions 35 for user specified hunk header patterns. 36 37* "git gc" when ejecting otherwise unreachable objects from packfiles into 38 loose form leaked memory. 39 40* "git index-pack" was recently broken and mishandled objects added by 41 thin-pack completion processing under memory pressure. 42 43* "git index-pack" was recently broken and misbehaved when run from inside 44 .git/objects/pack/ directory. 45 46* "git stash apply sash@{1}" was fixed to error out. Prior versions 47 would have applied stash@{0} incorrectly. 48 49* "git stash apply" now offers a better suggestion on how to continue 50 if the working tree is currently dirty. 51 52* "git for-each-ref --format=%(subject)" fixed for commits with no 53 no newline in the message body. 54 55* "git remote" fixed to protect printf from user input. 56 57* "git remote show -v" now displays all URLs of a remote. 58 59* "git checkout -b branch" was confused when branch already existed. 60 61* "git checkout -q" once again suppresses the locally modified file list. 62 63* "git clone -q", "git fetch -q" asks remote side to not send 64 progress messages, actually making their output quiet. 65 66* Cross-directory renames are no longer used when creating packs. This 67 allows more graceful behavior on filesystems like sshfs. 68 69* Stale temporary files under $GIT_DIR/objects/pack are now cleaned up 70 automatically by "git prune". 71 72* "git merge" once again removes directories after the last file has 73 been removed from it during the merge. 74 75* "git merge" did not allocate enough memory for the structure itself when 76 enumerating the parents of the resulting commit. 77 78* "git blame -C -C" no longer segfaults while trying to pass blame if 79 it encounters a submodule reference. 80 81* "git rm" incorrectly claimed that you have local modifications when a 82 path was merely stat-dirty. 83 84* "git svn" fixed to display an error message when 'set-tree' failed, 85 instead of a Perl compile error. 86 87* "git submodule" fixed to handle checking out a different commit 88 than HEAD after initializing the submodule. 89 90* The "git commit" error message when there are still unmerged 91 files present was clarified to match "git write-tree". 92 93* "git init" was confused when core.bare or core.sharedRepository are set 94 in system or user global configuration file by mistake. When --bare or 95 --shared is given from the command line, these now override such 96 settings made outside the repositories. 97 98* Some segfaults due to uncaught NULL pointers were fixed in multiple 99 tools such as apply, reset, update-index. 100 101* Solaris builds now default to OLD_ICONV=1 to avoid compile warnings; 102 Solaris 8 does not define NEEDS_LIBICONV by default. 103 104* "Git.pm" tests relied on unnecessarily more recent version of Perl. 105 106* "gitweb" triggered undef warning on commits without log messages. 107 108* "gitweb" triggered undef warnings on missing trees. 109 110* "gitweb" now removes PATH_INFO from its URLs so users don't have 111 to manually set the URL in the gitweb configuration. 112 113* Bash completion removed support for legacy "git-fetch", "git-push" 114 and "git-pull" as these are no longer installed. Dashless form 115 ("git fetch") is still however supported. 116 117Many other documentation updates.