@@ -149,7 +149,7 @@ UI, Workflows & Features
149149 * Many long-running operations show progress eye-candy, even when
150150 they are later backgrounded. Hide the eye-candy when the process
151151 is sent to the background instead.
152- (merge 9a9a41d lm/squelch-bg-progress later to maint).
152+ (merge a4fb76c lm/squelch-bg-progress later to maint).
153153
154154
155155Performance, Internal Implementation, Development Support etc.
@@ -231,7 +231,7 @@ notes for details).
231231
232232 * Memory usage of "git index-pack" has been trimmed by tens of
233233 per-cent.
234- (merge a78c5b3 nd/slim-index-pack-memory-usage later to maint).
234+ (merge f0e7f11 nd/slim-index-pack-memory-usage later to maint).
235235
236236 * "git rev-list --objects $old --not --all" to see if everything that
237237 is reachable from $old is already connected to the existing refs
@@ -339,19 +339,6 @@ notes for details).
339339 the order was swapped from the beginning. This belatedly fixes it.
340340 (merge 099d2d8 jc/gitignore-precedence later to maint).
341341
342- * After "git add -N", the path appeared in output of "git diff HEAD"
343- and "git diff --cached HEAD", leading "git status" to classify it
344- as "Changes to be committed". Such a path, however, is not yet to
345- be scheduled to be committed. "git diff" showed the change to the
346- path as modification, not as a "new file", in the header of its
347- output.
348-
349- Treat such paths as "yet to be added to the index but Git already
350- know about them"; "git diff HEAD" and "git diff --cached HEAD"
351- should not talk about them, and "git diff" should show them as new
352- files yet to be added to the index.
353- (merge d95d728 nd/diff-i-t-a later to maint).
354-
355342 * There was a commented-out (instead of being marked to expect
356343 failure) test that documented a breakage that was fixed since the
357344 test was written; turn it into a proper test.
0 commit comments