| 1 | Git v1.7.4.2 Release Notes |
| 2 | ========================== |
| 3 | |
| 4 | Fixes 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 | |
| 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 | |
| 15 | * "git bisect visualize" tried to run "gitk" in windowing |
| 16 | environments even when "gitk" is not installed, resulting in a |
| 17 | strange error message. |
| 18 | |
| 19 | * "git clone /no/such/path" did not fail correctly. |
| 20 | |
| 21 | * "git commit" did not correctly error out when the user asked to use a |
| 22 | non existent file as the commit message template. |
| 23 | |
| 24 | * "git diff --stat -B" ran on binary files counted the changes in lines, |
| 25 | which was nonsensical. |
| 26 | |
| 27 | * "git diff -M" opportunistically detected copies, which was not |
| 28 | necessarily a good thing, especially when it is internally run by |
| 29 | recursive merge. |
| 30 | |
| 31 | * "git difftool" didn't tell (g)vimdiff that the files it is reading are |
| 32 | to be opened read-only. |
| 33 | |
| 34 | * "git merge" didn't pay attention to prepare-commit-msg hook, even |
| 35 | though if a merge is conflicted and manually resolved, the subsequent |
| 36 | "git commit" would have triggered the hook, which was inconsistent. |
| 37 | |
| 38 | * "git patch-id" (and commands like "format-patch --ignore-in-upstream" |
| 39 | that use it as their internal logic) handled changes to files that end |
| 40 | with incomplete lines incorrectly. |
| 41 | |
| 42 | * The official value to tell "git push" to push the current branch back |
| 43 | to update the upstream branch it forked from is now called "upstream". |
| 44 | The old name "tracking" is and will be supported. |
| 45 | |
| 46 | * "git submodule update" used to honor the --merge/--rebase option (or |
| 47 | corresponding configuration variables) even for a newly cloned |
| 48 | subproject, which made no sense (so/submodule-no-update-first-time). |
| 49 | |
| 50 | * gitweb's "highlight" interface mishandled tabs. |
| 51 | |
| 52 | * gitweb didn't understand timezones with GMT offset that is not |
| 53 | multiple of a whole hour. |
| 54 | |
| 55 | * gitweb had a few forward-incompatible syntactic constructs and |
| 56 | also used incorrect variable when showing the file mode in a diff. |
| 57 | |
| 58 | And other minor fixes and documentation updates. |