| blob | c6ea0acb9a5d46044faffa24be6f6bc4b1dba82d |
1 Git 1.7.12.1 Release Notes
2 ==========================
4 Fixes since v1.7.12
5 -------------------
7 * "ciabot" script (in contrib/) has been updated with extensive
8 documentation.
10 * The "--rebase" option to "git pull" can be abbreviated to "-r",
11 but we didn't document it.
13 * It was generally understood that "--long-option"s to many of our
14 subcommands can be abbreviated to the unique prefix, but it was not
15 easy to find it described for new readers of the documentation set.
17 * The "--topo-order", "--date-order" (and the lack of either means
18 the default order) options to "rev-list" and "log" family of
19 commands were poorly described in the documentation.
21 * Older parts of the documentation described as if having a regular
22 file in .git/refs/ hierarchy were the only way to have branches and
23 tags, which is not true for quite some time.
25 * A utility shell function test_seq has been added as a replacement
26 for the 'seq' utility found on some platforms.
28 * Fallback 'getpass' implementation made unportable use of stdio API.
30 * "git commit --amend" let the user edit the log message and then
31 died when the human-readable committer name was given
32 insufficiently by getpwent(3).
34 * "git prune" without "-v" used to warn about leftover temporary
35 files (which is an indication of an earlier aborted operation).
37 * The reflog entries left by "git rebase" and "git rebase -i" were
38 inconsistent (the interactive one gave an abbreviated object name).
40 * When the user exports a non-default IFS without HT, scripts that
41 rely on being able to parse "ls-files -s | while read a b c..."
42 started to fail. Protect them from such a misconfiguration.
44 * When "git push" triggered the automatic gc on the receiving end, a
45 message from "git prune" that said it was removing cruft leaked to
46 the standard output, breaking the communication protocol.
48 * "git diff" had a confusion between taking data from a path in the
49 working tree and taking data from an object that happens to have
50 name 0{40} recorded in a tree.
52 * "git send-email" did not unquote encoded words that appear on the
53 header correctly, and lost "_" from strings.
55 * When the user gives an argument that can be taken as both a
56 revision name and a pathname without disambiguating with "--", we
57 used to give a help message "Use '--' to separate". The message
58 has been clarified to show where that '--' goes on the command
59 line.
61 * "gitweb" when used with PATH_INFO failed to notice directories with
62 SP (and other characters that need URL-style quoting) in them.