path: root/Documentation
diff options
authorJunio C Hamano <>2011-03-16 23:59:30 (GMT)
committerJunio C Hamano <>2011-03-16 23:59:30 (GMT)
commitb2f6eab4027beaaa7415e70dad269bdc7cc27722 (patch)
tree2e6088ca17b4042ccf9c658148cd5af55021c8a1 /Documentation
parent06316234accdcb6608506aed6600cd60ff5c5c8e (diff)
parentfbcda3c0a72cbcc105100ebef1b1dae54d854204 (diff)
Merge branch 'maint'
* maint: Prepare draft release notes to gitweb: highlight: replace tabs with spaces make_absolute_path: return the input path if it points to our buffer valgrind: ignore SSE-based strlen invalid reads diff --submodule: split into bite-sized pieces cherry: split off function to print output lines branch: split off function that writes tracking info and commit subject standardize brace placement in struct definitions compat: make gcc bswap an inline function enums: omit trailing comma for portability Conflicts: RelNotes
Diffstat (limited to 'Documentation')
1 files changed, 42 insertions, 0 deletions
diff --git a/Documentation/RelNotes/ b/Documentation/RelNotes/
new file mode 100644
index 0000000..afb3871
--- /dev/null
+++ b/Documentation/RelNotes/
@@ -0,0 +1,42 @@
+Git v1.7.4.2 Release Notes
+Fixes since v1.7.4.1
+ * Many documentation updates to match "git cmd -h" output and the
+ git-cmd manual page.
+ * "git clone /no/such/path" did not fail correctly.
+ * "git commit" did not correctly error out when the user asked to use a
+ non existent file as the commit message template.
+ * "git diff --stat -B" ran on binary files counted the changes in lines,
+ which was nonsensical.
+ * "git diff -M" opportunistically detected copies, which was not
+ necessarily a good thing, especially when it is internally run by
+ recursive merge.
+ * "git difftool" didn't tell (g)vimdiff that the files it is reading are
+ to be opened read-only.
+ * "git merge" didn't pay attention to prepare-commit-msg hook, even
+ though if a merge is conflicted and manually resolved, the subsequent
+ "git commit" would have triggered the hook, which was inconsistent.
+ * "git patch-id" (and commands like "format-patch --ignore-in-upstream"
+ that use it as their internal logic) handled changes to files that end
+ with incomplete lines incorrectly.
+ * The official value to tell "git push" to push the current branch back
+ to update the upstream branch it forked from is now called "upstream".
+ The old name "tracking" is and will be supported.
+ * gitweb's "highlight" interface mishandled tabs.
+ * gitweb had a few forward-incompatible syntactic constructs and
+ also used incorrect variable when showing the file mode in a diff.
+And other minor fixes and documentation updates.