@@ -4,9 +4,17 @@ Git v1.7.9.1 Release Notes
44Fixes since v1.7.9
55------------------
66
7+ * rpmbuild noticed an unpackaged but installed *.mo file and failed.
8+
79 * Subprocesses spawned from various git programs were often left running
810 to completion even when the top-level process was killed.
911
12+ * "git add -e" learned not to show a diff for an otherwise unmodified
13+ submodule that only has uncommitted local changes in the patch
14+ prepared by for the user to edit.
15+
16+ * Typo in "git branch --edit-description my-tpoic" was not diagnosed.
17+
1018 * Using "git grep -l/-L" together with options -W or --break may not
1119 make much sense as the output is to only count the number of hits
1220 and there is no place for file breaks, but the latter options made
@@ -16,14 +24,22 @@ Fixes since v1.7.9
1624 chain and veered into side branch from which the whole change to the
1725 specified paths came.
1826
27+ * "git merge --ff-only $tag" failed because it cannot record the
28+ required mergetag without creating a merge, but this is so common
29+ operation for branch that is used _only_ to follow the upstream, so
30+ it was changed to allow fast-forwarding without recording the mergetag.
31+
32+ * "git mergetool" now gives an empty file as the common base version
33+ to the backend when dealing with the "both sides added, differently"
34+ case.
35+
1936 * "git push -q" was not sufficiently quiet.
2037
2138 * When "git push" fails to update any refs, the client side did not
2239 report an error correctly to the end user.
2340
24- * "git mergetool" now gives an empty file as the common base version
25- to the backend when dealing with the "both sides added, differently"
26- case.
41+ * "rebase" and "commit --amend" failed to work on commits with ancient
42+ timestamps near year 1970.
2743
2844 * When asking for a tag to be pulled, "request-pull" did not show the
2945 name of the tag prefixed with "tags/", which would have helped older
0 commit comments