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