Re: correct git merge behavior or corner case?
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Apr 21, 2009, 09:04 UTC
- Message-ID
- <alpine.DEB.1.00.0904211103380.10279@pacific.mpi-cbg.de>
- In-Reply-To
- <fabb9a1e0904210200j5f82e9ci440b99ab18016938@mail.gmail.com>
Hi,
On Tue, 21 Apr 2009, Sverre Rabbelier wrote:
Show 19 quoted lines
> On Tue, Apr 21, 2009 at 10:56, Johannes Schindelin > <Johannes.Schindelin@gmx.de> wrote: > > But they would be a good example why we do _not_ want rename detection > > there. > > Yes, I would agree that they are indeed a good example. The other day > I moved a directory in a python project (containing several > sub-directories and as such several empty __init__.py files), and it > renamed them rather wrongly :P. > > The diff looked something like: > Renamed root/old/a/__init__.py to root/new/b/__init__.py > Renamed root/old/b/__init__.py to root/new/c/__init__.py > Renamed root/old/c/__init__.py to root/new/a/__init__.py > > While of course, a better result would have been: > Renamed root/old/a/__init__.py to root/new/a/__init__.py > Renamed root/old/b/__init__.py to root/new/b/__init__.py > Renamed root/old/c/__init__.py to root/new/c/__init__.py
Heh, at some point I had a patch in my tree (dunno if it still there) to use Levenshtein for rename detection, that should have helped...
Ciao, Dscho