@@ -50,6 +50,14 @@ UI, Workflows & Features
50
50
E.g. "foo/**/bar" matches "bar" in "foo" itself or in a
51
51
subdirectory of "foo".
52
52
53
+ * When giving arguments without "--" disambiguation, object names
54
+ that come earlier on the command line must not be interpretable as
55
+ pathspecs and pathspecs that come later on the command line must
56
+ not be interpretable as object names. This disambiguation rule has
57
+ been tweaked so that ":/" (no other string before or after) is
58
+ always interpreted as a pathspec; "git cmd -- :/" is no longer
59
+ needed, you can just say "git cmd :/".
60
+
53
61
* "git blame" (and "git diff") learned the "--no-follow" option.
54
62
55
63
* "git check-ignore" command to help debugging .gitignore files has
@@ -112,7 +120,8 @@ Foreign Interface
112
120
113
121
* A new remote helper to interact with bzr has been added to contrib/.
114
122
115
- * "git p4" got various bugfixes around its branch handling.
123
+ * "git p4" got various bugfixes around its branch handling. It is
124
+ also made usable with Python 2.4/2.5.
116
125
117
126
* The remote helper to interact with Hg in contrib/ has seen a few
118
127
fixes.
@@ -126,6 +135,11 @@ Performance, Internal Implementation, etc.
126
135
* Matching paths with common forms of pathspecs that contain wildcard
127
136
characters has been optimized further.
128
137
138
+ * We stopped paying attention to $GIT_CONFIG environment that points
139
+ at a single configuration file from any command other than "git config"
140
+ quite a while ago, but "git clone" internally set, exported, and
141
+ then unexported the variable during its operation unnecessarily.
142
+
129
143
* "git reset" internals has been reworked and should be faster in
130
144
general. We tried to be careful not to break any behaviour but
131
145
there could be corner cases, especially when running the command
@@ -153,6 +167,13 @@ Performance, Internal Implementation, etc.
153
167
USE_WILDMATCH, using the resulting Git daily and reporting when you
154
168
find breakages, you can help us get closer to that goal.
155
169
170
+ * Some reimplementations of Git do not write all the stat info back
171
+ to the index due to their implementation limitations (e.g. jgit).
172
+ A configuration option can tell Git to ignore changes to most of
173
+ the stat fields and only pay attention to mtime and size, which
174
+ these implementations can reliably update. This can be used to
175
+ avoid excessive revalidation of contents.
176
+
156
177
157
178
Also contains minor documentation updates and code clean-ups.
158
179
@@ -186,6 +207,11 @@ details).
186
207
* After failing to create a temporary file using mkstemp(), failing
187
208
pathname was not reported correctly on some platforms.
188
209
210
+ * We used to stuff "user@" and then append what we read from
211
+ /etc/mailname to come up with a default e-mail ident, but a bug
212
+ lost the "user@" part.
213
+ (merge dc342a2 jn/do-not-drop-username-when-reading-from-etc-mailname later to maint).
214
+
189
215
* The attribute mechanism didn't allow limiting attributes to be
190
216
applied to only a single directory itself with "path/" like the
191
217
exclude mechanism does. The initial implementation of this that
@@ -206,6 +232,10 @@ details).
206
232
* "git archive" did not record uncompressed size in the header when
207
233
streaming a zip archive, which confused some implementations of unzip.
208
234
235
+ * Attempt to "branch --edit-description" an existing branch, while
236
+ being on a detached HEAD, errored out.
237
+ (merge 75135b2 nd/edit-branch-desc-while-detached later to maint).
238
+
209
239
* "git clean" showed what it was going to do, but sometimes end up
210
240
finding that it was not allowed to do so, which resulted in a
211
241
confusing output (e.g. after saying that it will remove an
@@ -218,6 +248,12 @@ details).
218
248
failed to remove the real location of the $GIT_DIR it created.
219
249
This was most visible when interrupting a submodule update.
220
250
251
+ * "git fetch --depth" was broken in at least three ways. The
252
+ resulting history was deeper than specified by one commit, it was
253
+ unclear how to wipe the shallowness of the repository with the
254
+ command, and documentation was misleading.
255
+ (merge cfb70e1 nd/fetch-depth-is-broken later to maint).
256
+
221
257
* The way "git svn" asked for password using SSH_ASKPASS and
222
258
GIT_ASKPASS was not in line with the rest of the system.
223
259
@@ -306,3 +342,7 @@ details).
306
342
need to be in the cvsadmin group on NetBSD 6.0).
307
343
308
344
* t9020 and t9810 had a few non-portable shell script construct.
345
+
346
+ * Scripts to test bash completion was inherently flaky as it was
347
+ affected by whatever random things the user may have on $PATH.
348
+ (merge 5047822 jc/do-not-let-random-file-interfere-with-completion-tests later to maint).
0 commit comments