1Git v2.4.2 Release Notes 2======================== 3 4Fixes since v2.4.1 5------------------ 6 7 * "git rev-list --objects $old --not --all" to see if everything that 8 is reachable from $old is already connected to the existing refs 9 was very inefficient. 10 11 * "hash-object --literally" introduced in v2.2 was not prepared to 12 take a really long object type name. 13 14 * "git rebase --quiet" was not quite quiet when there is nothing to 15 do. 16 17 * The completion for "log --decorate=" parameter value was incorrect. 18 19 * "filter-branch" corrupted commit log message that ends with an 20 incomplete line on platforms with some "sed" implementations that 21 munge such a line. Work it around by avoiding to use "sed". 22 23 * "git daemon" fails to build from the source under NO_IPV6 24 configuration (regression in 2.4). 25 26 * "git stash pop/apply" forgot to make sure that not just the working 27 tree is clean but also the index is clean. The latter is important 28 as a stash application can conflict and the index will be used for 29 conflict resolution. 30 31 * We have prepended $GIT_EXEC_PATH and the path "git" is installed in 32 (typically "/usr/bin") to $PATH when invoking subprograms and hooks 33 for almost eternity, but the original use case the latter tried to 34 support was semi-bogus (i.e. install git to /opt/foo/git and run it 35 without having /opt/foo on $PATH), and more importantly it has 36 become less and less relevant as Git grew more mainstream (i.e. the 37 users would _want_ to have it on their $PATH). Stop prepending the 38 path in which "git" is installed to users' $PATH, as that would 39 interfere the command search order people depend on (e.g. they may 40 not like versions of programs that are unrelated to Git in /usr/bin 41 and want to override them by having different ones in /usr/local/bin 42 and have the latter directory earlier in their $PATH). 43 44Also contains typofixes, documentation updates and trivial code 45clean-ups.