@@ -69,6 +69,9 @@ Updates since v1.7.6
69
69
generation machinery stolen from jgit, which might give better
70
70
performance.
71
71
72
+ * "git diff" had a wierd worst case behaviour that can be triggered
73
+ when comparing files with potentially many places that could match.
74
+
72
75
* "git fetch", "git push" and friends no longer show connection
73
76
errors for addresses that couldn't be connected when at least one
74
77
address succeeds (this is arguably a regression but a deliberate
@@ -86,12 +89,22 @@ Updates since v1.7.6
86
89
* "git rebase master topci" no longer spews usage hints after giving
87
90
"fatal: no such branch: topci" error message.
88
91
92
+ * The recursive merge strategy implementation got a fairly large
93
+ fixes for many corner cases that may rarely happen in real world
94
+ projects (it has been verified that none of the 16000+ merges in
95
+ the Linux kernel history back to v2.6.12 is affected with the
96
+ corner case bugs this update fixes).
97
+
89
98
* "git stash" learned --include-untracked option.
90
99
91
100
* "git submodule update" used to stop at the first error updating a
92
101
submodule; it now goes on to update other submodules that can be
93
102
updated, and reports the ones with errors at the end.
94
103
104
+ * "git push" can be told with --recurse-submodules=check option to
105
+ refuse pushing of the supermodule, if any of its submodules'
106
+ commits hasn't been pushed out to their remotes.
107
+
95
108
* "git upload-pack" and "git receive-pack" learned to pretend only a
96
109
subset of the refs exist in a repository. This may help a site to
97
110
put many tiny repositories into one repository (this would not be
0 commit comments