1Git v2.12.3 Release Notes 2========================= 3 4Fixes since v2.12.2 5------------------- 6 7 * The "parse_config_key()" API function has been cleaned up. 8 9 * An helper function to make it easier to append the result from 10 real_path() to a strbuf has been added. 11 12 * The t/perf performance test suite was not prepared to test not so 13 old versions of Git, but now it covers versions of Git that are not 14 so ancient. 15 16 * Picking two versions of Git and running tests to make sure the 17 older one and the newer one interoperate happily has now become 18 possible. 19 20 * Teach the "debug" helper used in the test framework that allows a 21 command to run under "gdb" to make the session interactive. 22 23 * "git repack --depth=<n>" for a long time busted the specified depth 24 when reusing delta from existing packs. This has been corrected. 25 26 * user.email that consists of only cruft chars should consistently 27 error out, but didn't. 28 29 * A few tests were run conditionally under (rare) conditions where 30 they cannot be run (like running cvs tests under 'root' account). 31 32 * "git branch @" created refs/heads/@ as a branch, and in general the 33 code that handled @{-1} and @{upstream} was a bit too loose in 34 disambiguating. 35 36 * "git fetch" that requests a commit by object name, when the other 37 side does not allow such an request, failed without much 38 explanation. 39 40 * "git filter-branch --prune-empty" drops a single-parent commit that 41 becomes a no-op, but did not drop a root commit whose tree is empty. 42 43 * Recent versions of Git treats http alternates (used in dumb http 44 transport) just like HTTP redirects and requires the client to 45 enable following it, due to security concerns. But we forgot to 46 give a warning when we decide not to honor the alternates. 47 48 * NO_PTHREADS build has been broken for some time; now fixed. 49 50 * Fix for potential segv introduced in v2.11.0 and later (also 51 v2.10.2). 52 53 * A few unterminated here documents in tests were fixed, which in 54 turn revealed incorrect expectations the tests make. These tests 55 have been updated. 56 57Also contains various documentation updates and code clean-ups.