Re: bisect / history preserving on rename + update
- From
- Thomas Gleixner <tglx@linutronix.de>
- Date
- Aug 14, 2007, 10:16 UTC
- Message-ID
- <1187086600.12828.177.camel@chaos>
- In-Reply-To
- <20070814093357.GA14010@diana.vm.bytemark.co.uk>
On Tue, 2007-08-14 at 11:33 +0200, Karl Hasselström wrote:
Show 18 quoted lines
> On 2007-08-14 10:38:01 +0200, Thomas Gleixner wrote: > > > is there a built in way to handle the following situation: > > > > file A is renamed to B > > file A is created again and new content is added. > > > > I found only two ways to do that, which both suck: > > > > 1) > > git-mv A B > > git-add A > > git commit > > > > results in a copy A to B and lost history of B > > What exactly do you mean by "lost history of B"? You do know that git > doesn't record renames? So you could just as well do
Err.
git-mv A B git commit edit B git commit git blame B <- shows the full history of A & B
IMHO that's why we have git-mv
tglx