@@ -4,9 +4,17 @@ Git v1.7.9.1 Release Notes
4
4
Fixes since v1.7.9
5
5
------------------
6
6
7
+ * rpmbuild noticed an unpackaged but installed *.mo file and failed.
8
+
7
9
* Subprocesses spawned from various git programs were often left running
8
10
to completion even when the top-level process was killed.
9
11
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
+
10
18
* Using "git grep -l/-L" together with options -W or --break may not
11
19
make much sense as the output is to only count the number of hits
12
20
and there is no place for file breaks, but the latter options made
@@ -16,14 +24,22 @@ Fixes since v1.7.9
16
24
chain and veered into side branch from which the whole change to the
17
25
specified paths came.
18
26
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
+
19
36
* "git push -q" was not sufficiently quiet.
20
37
21
38
* When "git push" fails to update any refs, the client side did not
22
39
report an error correctly to the end user.
23
40
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.
27
43
28
44
* When asking for a tag to be pulled, "request-pull" did not show the
29
45
name of the tag prefixed with "tags/", which would have helped older
0 commit comments