| blob | afb387161b6c14a2792e0164bf8ff32741764d0d |
1 Git v1.7.4.2 Release Notes
2 ==========================
4 Fixes since v1.7.4.1
5 --------------------
7 * Many documentation updates to match "git cmd -h" output and the
8 git-cmd manual page.
10 * "git clone /no/such/path" did not fail correctly.
12 * "git commit" did not correctly error out when the user asked to use a
13 non existent file as the commit message template.
15 * "git diff --stat -B" ran on binary files counted the changes in lines,
16 which was nonsensical.
18 * "git diff -M" opportunistically detected copies, which was not
19 necessarily a good thing, especially when it is internally run by
20 recursive merge.
22 * "git difftool" didn't tell (g)vimdiff that the files it is reading are
23 to be opened read-only.
25 * "git merge" didn't pay attention to prepare-commit-msg hook, even
26 though if a merge is conflicted and manually resolved, the subsequent
27 "git commit" would have triggered the hook, which was inconsistent.
29 * "git patch-id" (and commands like "format-patch --ignore-in-upstream"
30 that use it as their internal logic) handled changes to files that end
31 with incomplete lines incorrectly.
33 * The official value to tell "git push" to push the current branch back
34 to update the upstream branch it forked from is now called "upstream".
35 The old name "tracking" is and will be supported.
37 * gitweb's "highlight" interface mishandled tabs.
39 * gitweb had a few forward-incompatible syntactic constructs and
40 also used incorrect variable when showing the file mode in a diff.
42 And other minor fixes and documentation updates.