[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

AW: What is the scenario for this warning?

From: Paul Maier <svn-user_at_web.de>
Date: Sat, 27 Nov 2010 13:30:36 +0100

Hi Daniel,

thanks for the explanation.

I don't understand the part with the recursion:
The mergeinfo is stored in the property svn:mergeinfo in the directory.
When I copy this directory from WC to a new directory in WC,
will the property svn:mergeinfo be set in the copy?

Thanks.
  Paul.
 

> -----Ursprüngliche Nachricht-----
> Von: Daniel Shahaf [mailto:d.s_at_daniel.shahaf.name]
> Gesendet: Samstag, 27. November 2010 08:49
> An: Paul Maier
> Cc: users_at_subversion.apache.org
> Betreff: Re: What is the scenario for this warning?
>
> I think the problem is: if a file inherits mergeinfo from somewhere
> above the wc root, then that mergeinfo won't be preserved in the copy
> target.
>
> In other words, svn will recurse to find a parent/ancestor from which
> mergeinfo is inherited only up to the wc root, but won't
> connect to the
> repository to investigate whether mergeinfo is inherited from
> a parent/ancestor of the wc root. So, typically, this should only be
> a concern if you're working in a wc whose root is not a branch root.
>
> (I have a feeling this wasn't quite clear at all...)
>
> Daniel
>
>
> Paul Maier wrote on Sat, Nov 27, 2010 at 01:30:09 +0100:
> > Hello!
> >
> > I'm used to "svn cp" within the same WC, everything seems
> to work fine.
> > I just read this warning and now I wonder if this is
> relevant for my use case.
> >
> > svn help cp
> > [...]
> > WARNING: For compatibility with previous versions of Subversion,
> > copies performed using two working copy paths (WC -> WC) will not
> > contact the repository. As such, they may not, by default, be able
> > to propagate merge tracking information from the source of the copy
> > to the destination.
> >
> > Thanks!
> > Paul
> >
Received on 2010-11-27 13:32:31 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.