[Kde-scm-interest] svn help

[Andreas Pakulat]

On 03.03.10 15:48:26, Torgny Nyblom wrote:
> On Wednesday 03 March 2010 12.59.58 Andreas Pakulat wrote:
> > On 03.03.10 11:40:34, Torgny Nyblom wrote:
> > > Hi,
> > > 
> > > I'm currently trying to get some rules together for the kdepim and
> > > kdepimlibs modules...
> > > 
> > > Some questions:
> > > 
> > > * It seems like "svn log --stop-on-copy" does not work when "svn mv" was
> > > used. Is there a way to get the same result for this case (as for when
> > > "svn cp" was used)?
> > > Unfortunately the pim modules are quite full of these "svn mv ..."
> > > commands.
> > 
> > Can you provide an example where this doesn't work? svn mv is the same as
> > svn cp + svn remove, except its in one commit. I have seen several moves in
> > the kdevelop history and --stop-on-copy always stopped on them.
> 
> Take kdepim  there the command doesn't stop until on r455551 (a copy from the 
> 3.5 branch to trunk) but there has been a lot of modules moved in after that. 
> For instance KMail was replaced from the work/akonadi-ports branch in 
> r1076571.

You won't see that with an svn log --stop-on-copy .../trunk/KDE/kdepim, you
only see it when doing it for kmail directly with: svn log --stop-on-copy
..../trunk/KDE/kdepim/kmail. The stop-on-copy is effective for the path you
give to it.

Its however easy to find such copies with a simple search in the output of
svn log, simply look for "A.*from:" entries

Andreas

-- 
Be security conscious -- National defense is at stake.