diff options
author | Junio C Hamano <gitster@pobox.com> | 2014-04-03 13:37:29 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2014-04-03 13:40:00 -0700 |
commit | 2f91649a9ba7c590be4f1ce66521b21e305fb7bc (patch) | |
tree | 951cc745c18ae97ae356822c626d79dc6c239731 /Documentation/RelNotes/1.9.2.txt | |
parent | 3097b687bea8817b4b0afd84db8c4b1079cea92f (diff) | |
download | git-2f91649a9ba7c590be4f1ce66521b21e305fb7bc.tar.gz |
Start preparing for 1.9.1
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/RelNotes/1.9.2.txt')
-rw-r--r-- | Documentation/RelNotes/1.9.2.txt | 38 |
1 files changed, 38 insertions, 0 deletions
diff --git a/Documentation/RelNotes/1.9.2.txt b/Documentation/RelNotes/1.9.2.txt new file mode 100644 index 0000000000..c755e349d3 --- /dev/null +++ b/Documentation/RelNotes/1.9.2.txt @@ -0,0 +1,38 @@ +Git v1.9.2 Release Notes +======================== + +Fixes since v1.9.1 +------------------ + + * "git mv" that moves a submodule forgot to adjust the array that + uses to keep track of which submodules were to be moved to update + its configuration. + + * Length limit for the pathname used when removing a path in a deep + subdirectory has been removed to avoid buffer overflows. + + * The test helper lib-terminal always run an actual test_expect_* + when included, which screwed up with the use of skil-all that may + have to be done later. + + * "git index-pack" used a wrong variable to name the keep-file in an + error message when the file cannot be written or closed. + + * "rebase -i" produced a broken insn sheet when the title of a commit + happened to contain '\n' (or ended with '\c') due to a careless use + of 'echo'. + + * There were a few instances of 'git-foo' remaining in the + documentation that should have been spelled 'git foo'. + + * Serving objects from a shallow repository needs to write a + new file to hold the temporary shallow boundaries but it was not + cleaned when we exit due to die() or a signal. + + * When "git stash pop" stops after failing to apply the stash + (e.g. due to conflicting changes), the stash is not dropped. State + that explicitly in the output to let the users know. + + * The labels in "git status" output that describe the nature of + conflicts (e.g. "both deleted") were limited to 20 bytes, which was + too short for some l10n (e.g. fr). |