Skip to content

Commit 2161ed8

Browse files
newrengitster
authored andcommitted
RelNotes: remove duplicate release note
In the 2.18 cycle, directory rename detection was merged, then reverted, then reworked in such a way to fix another prominent bug in addition to the original problem causing it to be reverted. When the reworked series was merged, we ended up with two nearly duplicate release notes. Remove the second copy, but preserve the information about the extra bug fix. Signed-off-by: Elijah Newren <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 12039e0 commit 2161ed8

File tree

1 file changed

+3
-11
lines changed

1 file changed

+3
-11
lines changed

Documentation/RelNotes/2.18.0.txt

Lines changed: 3 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,9 @@ UI, Workflows & Features
1212
want to move to z/d by taking the hint that the entire directory
1313
'x' moved to 'z'. A bug causing dirty files involved in a rename
1414
to be overwritten during merge has also been fixed as part of this
15-
work.
15+
work. Incidentally, this also avoids updating a file in the
16+
working tree after a (non-trivial) merge whose result matches what
17+
our side originally had.
1618

1719
* "git filter-branch" learned to use a different exit code to allow
1820
the callers to tell the case where there was no new commits to
@@ -256,16 +258,6 @@ Performance, Internal Implementation, Development Support etc.
256258
repository object (which in turn tells the API which object store
257259
the objects are to be located).
258260

259-
* Rename detection logic in "diff" family that is used in "merge" has
260-
learned to guess when all of x/a, x/b and x/c have moved to z/a,
261-
z/b and z/c, it is likely that x/d added in the meantime would also
262-
want to move to z/d by taking the hint that the entire directory
263-
'x' moved to 'z'. A bug causing dirty files involved in a rename
264-
to be overwritten during merge has also been fixed as part of this
265-
work. Incidentally, this also avoids updating a file in the
266-
working tree after a (non-trivial) merge whose result matches what
267-
our side originally had.
268-
269261
* "git pack-objects" needs to allocate tons of "struct object_entry"
270262
while doing its work, and shrinking its size helps the performance
271263
quite a bit.

0 commit comments

Comments
 (0)