[Kde-scm-interest] Re: Tracking directory moves

[Arno Rehn]

On Monday 22 November 2010 18:29:53 Thiago Macieira wrote:
> Em Segunda-feira, 22 de Novembro de 2010, às 18:09:00, Arno Rehn escreveu:
> > (Sorry Niko for sending the initial reply directly to you, KMail didn't
> > realize that this is a mailing list...)
> > 
> > On Monday 22 November 2010 17:49:18 you wrote:
> > > 2010/11/22 Arno Rehn <kde at arnorehn.de>:
> > > > Hi again,
> > > > 
> > > > while tracking down the last issue, I've also found out that svn2git
> > > > won't currently track the move from kdebindings/qtruby to
> > > > kdebindings/ruby/qtruby. I thought an 'action recurse' rule on
> > > > /trunk/KDE/kdebindings/ruby/qtruby/ would fix this, but apparently it
> > > > doesn't.
> > > > Does anyone know what's wrong with the rules? (Rules attached).
> > > > The relevant commit is r653117 [0].
> > > 
> > > You convert into one git repository, svn2git can't help.
> > > 
> > > If you create multiple repositories with svn2git - instead of
> > > splitting afterwards - you
> > > can use recurse on kdebindings (not on ruby itself).
> > > But recurse won't be needed for this particular move anyway - you need
> > > it eg. when the whole KDE was tagged.
> > 
> > Hum. Alright, what do I need to do then to keep the whole history of the
> > moved files? Currently history starts at commit 653117 (i.e. the commit
> > where stuff was moved) - everything before that is not there, or rather,
> > not connected with those moved files. (I can check out a branch before
> > the move for example and then I have all that history, of course. But
> > since the files were just moved, I'd expect this history to show up for
> > the current files, too).
> 
> git log -M
Ah, got it. (git log --follow was actually what I was looking for, but 
anyway.. your answer made me look into the man-page)
Please feel free to slap me with a man-page next time I ask such things. :)

-- 
Arno Rehn
arno at arnorehn.de