1Git v1.7.10 Release Notes 2========================= 3 4Updates since v1.7.9 5-------------------- 6 7UI, Workflows & Features 8 9 * Improved handling of views, labels and branches in git-p4 (in contrib). 10 11 * "git am" learned to pass "-b" option to underlying "git mailinfo", so 12 that bracketed string other than "PATCH" at the beginning can be kept. 13 14 * "git clone" learned "--single-branch" option to limit cloning to a 15 single branch (surprise!). 16 17 * "git clone" learned to detach the HEAD in the resulting repository 18 when the source repository's HEAD does not point to a branch. 19 20 * When showing a patch while ignoring whitespace changes, the context 21 lines are taken from the postimage, in order to make it easier to 22 view the output. 23 24 * "git merge" in an interactive session learned to spawn the editor 25 by default to let the user edit the auto-generated merge message, 26 to encourage people to explain their merges better. Legacy scripts 27 can export MERGE_AUTOEDIT=no to retain the historical behaviour. 28 29Performance 30 31 * During "git upload-pack" in respose to "git fetch", unnecessary calls 32 to parse_object() have been eliminated, to help performance in 33 repositories with excessive number of refs. 34 35Internal Implementation 36 37 * Recursive call chains in "git index-pack" to deal with long delta 38 chains have been flattened, to reduce the stack footprint. 39 40 * Use of add_extra_ref() API is slowly getting removed, to make it 41 possible to cleanly restructure the overall refs API. 42 43 * The test suite supports the new "test_pause" helper function. 44 45 * t/Makefile is adjusted to prevent newer versions of GNU make from 46 running tests in seemingly random order. 47 48Also contains minor documentation updates and code clean-ups. 49 50 51Fixes since v1.7.9 52------------------ 53 54Unless otherwise noted, all the fixes since v1.7.9 in the maintenance 55releases are contained in this release (see release notes to them for 56details). 57 58 * When "git push" fails to update any refs, the client side did not 59 report an error correctly to the end user. 60 (merge 5238cbf sp/smart-http-failure-to-push later to maint). 61 62 * "git push -q" was not sufficiently quiet. 63 (merge d336572 cb/push-quiet later to maint). 64 65 * "git log --first-parent $pathspec" did not stay on the first parent 66 chain and veered into side branch from which the whole change to the 67 specified paths came. 68 (merge 36ed191 jc/maint-log-first-parent-pathspec later to maint). 69 70 * Subprocesses spawned from various git programs were often left running 71 to completion even when the top-level process was killed. 72 (merge 10c6cdd cb/maint-kill-subprocess-upon-signal later to maint). 73 74 * "git mergetool" now gives an empty file as the common base version 75 to the backend when dealing with the "both sides added, differently" 76 case. 77 (merge ec245ba da/maint-mergetool-twoway later to maint). 78 79 * "git submodule add $path" forgot to recompute the name to be stored 80 in .gitmodules when the submodule at $path was once added to the 81 superproject and already initialized. 82 (merge 1017c1a jl/submodule-re-add later to maint). 83 84 * Using "git grep -l/-L" together with options -W or --break may not 85 make much sense as the output is to only count the number of hits 86 and there is no place for file breaks, but the latter options made 87 "-l/-L" to miscount the hits. 88 (merge 50dd0f2 tr/grep-l-with-decoration later to maint). 89 90--- 91exec >/var/tmp/1 92O=v1.7.9-110-g873ce7c 93echo O=$(git describe) 94git log --first-parent --oneline ^maint $O.. 95echo 96git shortlog --no-merges ^maint $O..