[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Git Migration Needs YOU!
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2010-03-03 6:50:49
Message-ID: 20100303065049.GA14209 () trinity ! apaku ! dnsalias ! org
[Download RAW message or body]

On 03.03.10 00:00:46, Thiago Macieira wrote:
> Em Terça-feira 2. Março 2010, às 23.43.34, Aaron J. Seigo escreveu:
> > > Also the part about the recurse-action is empty as I don't understand
> > > what this is meant for/how it works. I've asked on kde-scm-interest on
> > > Sunday, but got no answer thus far.
> > 
> > hm.. hopefully someone in-the-know (thiago? :) can weigh in on this.
> 
> The recurse action is a hack to tell svn2git to recurse into a directory it 
> has just copied or that existed, because it's interesting.
> 
> Quick example:
> 
> We're importing kdelibs, so it exists in
> 	trunk/KDE/kdelibs
> 
> At branching, someone did:
> 	svn cp $SVNROOT/trunk/KDE $SVNROOT/branches/KDE/4.4
> 
> SVN recorded in that commit that branches/KDE/4.4 was the only path changed. 
> That means the rule branches/KDE/[^/]+/kdelibs/ will not match.
> 
> We need to tell the tool that something interesting happened inside and it 
> should recurse. Then it will apply again all rules to the files that exist at 
> that point, at which point the rules will match.

Just to be 100% clear on this, the recurse rule would be:

match /branches/KDE/4.4
  action recurse
end match

Right?

Andreas

-- 
You may be gone tomorrow, but that doesn't mean that you weren't here today.
[prev in list] [next in list] [prev in thread] [next in thread]