|
| 1 | +Git v1.9.2 Release Notes |
| 2 | +======================== |
| 3 | + |
| 4 | +Fixes since v1.9.1 |
| 5 | +------------------ |
| 6 | + |
| 7 | + * "git mv" that moves a submodule forgot to adjust the array that |
| 8 | + uses to keep track of which submodules were to be moved to update |
| 9 | + its configuration. |
| 10 | + |
| 11 | + * Length limit for the pathname used when removing a path in a deep |
| 12 | + subdirectory has been removed to avoid buffer overflows. |
| 13 | + |
| 14 | + * The test helper lib-terminal always run an actual test_expect_* |
| 15 | + when included, which screwed up with the use of skil-all that may |
| 16 | + have to be done later. |
| 17 | + |
| 18 | + * "git index-pack" used a wrong variable to name the keep-file in an |
| 19 | + error message when the file cannot be written or closed. |
| 20 | + |
| 21 | + * "rebase -i" produced a broken insn sheet when the title of a commit |
| 22 | + happened to contain '\n' (or ended with '\c') due to a careless use |
| 23 | + of 'echo'. |
| 24 | + |
| 25 | + * There were a few instances of 'git-foo' remaining in the |
| 26 | + documentation that should have been spelled 'git foo'. |
| 27 | + |
| 28 | + * Serving objects from a shallow repository needs to write a |
| 29 | + new file to hold the temporary shallow boundaries but it was not |
| 30 | + cleaned when we exit due to die() or a signal. |
| 31 | + |
| 32 | + * When "git stash pop" stops after failing to apply the stash |
| 33 | + (e.g. due to conflicting changes), the stash is not dropped. State |
| 34 | + that explicitly in the output to let the users know. |
| 35 | + |
| 36 | + * The labels in "git status" output that describe the nature of |
| 37 | + conflicts (e.g. "both deleted") were limited to 20 bytes, which was |
| 38 | + too short for some l10n (e.g. fr). |
0 commit comments