Update draft release notes to 1.7.4.2
[git/git.git] / Documentation / RelNotes / 1.7.4.2.txt
CommitLineData
fbcda3c0
JH
1Git v1.7.4.2 Release Notes
2==========================
3
4Fixes since v1.7.4.1
5--------------------
6
7 * Many documentation updates to match "git cmd -h" output and the
8 git-cmd manual page.
9
d98f24cd
JH
10 * We used to keep one file descriptor open for each and every packfile
11 that we have a mmap window on it (read: "in use"), even when for very
12 tiny packfiles. We now close the file descriptor early when the entire
13 packfile fits inside one mmap window.
14
fbcda3c0
JH
15 * "git clone /no/such/path" did not fail correctly.
16
17 * "git commit" did not correctly error out when the user asked to use a
18 non existent file as the commit message template.
19
20 * "git diff --stat -B" ran on binary files counted the changes in lines,
21 which was nonsensical.
22
23 * "git diff -M" opportunistically detected copies, which was not
24 necessarily a good thing, especially when it is internally run by
25 recursive merge.
26
27 * "git difftool" didn't tell (g)vimdiff that the files it is reading are
28 to be opened read-only.
29
30 * "git merge" didn't pay attention to prepare-commit-msg hook, even
31 though if a merge is conflicted and manually resolved, the subsequent
32 "git commit" would have triggered the hook, which was inconsistent.
33
34 * "git patch-id" (and commands like "format-patch --ignore-in-upstream"
35 that use it as their internal logic) handled changes to files that end
36 with incomplete lines incorrectly.
37
38 * The official value to tell "git push" to push the current branch back
39 to update the upstream branch it forked from is now called "upstream".
40 The old name "tracking" is and will be supported.
41
d98f24cd
JH
42 * "git submodule update" used to honor the --merge/--rebase option (or
43 corresponding configuration variables) even for a newly cloned
44 subproject, which made no sense (so/submodule-no-update-first-time).
45
fbcda3c0
JH
46 * gitweb's "highlight" interface mishandled tabs.
47
48 * gitweb had a few forward-incompatible syntactic constructs and
49 also used incorrect variable when showing the file mode in a diff.
50
51And other minor fixes and documentation updates.