| 1 | Git v2.30.1 Release Notes |
| 2 | ========================= |
| 3 | |
| 4 | This release is primarily to merge fixes accumulated on the 'master' |
| 5 | front to prepare for 2.31 release that are still relevant to 2.30.x |
| 6 | maintenance track. |
| 7 | |
| 8 | Fixes since v2.30 |
| 9 | ----------------- |
| 10 | |
| 11 | * "git fetch --recurse-submodules" failed to update a submodule |
| 12 | when it has an uninitialized (hence of no interest to the user) |
| 13 | sub-submodule, which has been corrected. |
| 14 | |
| 15 | * Command line error of "git rebase" are diagnosed earlier. |
| 16 | |
| 17 | * "git stash" did not work well in a sparsely checked out working |
| 18 | tree. |
| 19 | |
| 20 | * Some tests expect that "ls -l" output has either '-' or 'x' for |
| 21 | group executable bit, but setgid bit can be inherited from parent |
| 22 | directory and make these fields 'S' or 's' instead, causing test |
| 23 | failures. |
| 24 | |
| 25 | * "git for-each-repo --config=<var> <cmd>" should not run <cmd> for |
| 26 | any repository when the configuration variable <var> is not defined |
| 27 | even once. |
| 28 | |
| 29 | * "git mergetool --tool-help" was broken in 2.29 and failed to list |
| 30 | all the available tools. |
| 31 | |
| 32 | * Fix for procedure to building CI test environment for mac. |
| 33 | |
| 34 | * Newline characters in the host and path part of git:// URL are |
| 35 | now forbidden. |
| 36 | |
| 37 | * When more than one commit with the same patch ID appears on one |
| 38 | side, "git log --cherry-pick A...B" did not exclude them all when a |
| 39 | commit with the same patch ID appears on the other side. Now it |
| 40 | does. |
| 41 | |
| 42 | * Documentation for "git fsck" lost stale bits that has become |
| 43 | incorrect. |
| 44 | |
| 45 | * Doc for packfile URI feature has been clarified. |
| 46 | |
| 47 | * The implementation of "git branch --sort" wrt the detached HEAD |
| 48 | display has always been hacky, which has been cleaned up. |
| 49 | |
| 50 | * Our setting of GitHub CI test jobs were a bit too eager to give up |
| 51 | once there is even one failure found. Tweak the knob to allow |
| 52 | other jobs keep running even when we see a failure, so that we can |
| 53 | find more failures in a single run. |
| 54 | |
| 55 | Also contains minor documentation updates and code clean-ups. |