Re: correct git merge behavior or corner case?
- From
Sverre Rabbelier <srabbelier@gmail.com>
- Date
- Apr 21, 2009, 09:00 UTC
- Message-ID
- <fabb9a1e0904210200j5f82e9ci440b99ab18016938@mail.gmail.com>
- In-Reply-To
- <alpine.DEB.1.00.0904211055160.10279@pacific.mpi-cbg.de>
Heya,
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
-- Cheers, Sverre Rabbelier