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

Re: svn:mergeinfo questionable behavior

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Wed, 5 Jan 2011 13:14:54 +0100

On Wed, Jan 5, 2011 at 00:09, Thomas Charron <twaffle_at_gmail.com> wrote:
> I am encountering some..  'strange' behavior, with merging branches.
>  At some point, a given file in one of my repositories had a
> svn:mergeinfo property set on the file.  Let's call it foo.c.
>
>  So, in trunk, I have a *self referencing* svn:mergeinfo property.
> Looking at this files mergeinfo:
>
> /trunk/foo.c:1-5
>
>  Why would a file have a mergeinfo property refering to *itself*.
> It's illogical.  Are my developers doing something wrong?  It gets
> *REALLY* out of wack once I branch trunk, which brings these
> properties over, and then rebase back to trunk, leading to conflicts
> in the mergeinfo due to the change in the already strange looking self
> reference in the mergeinfo property.

Wrong mailing list:
first, this is not a question about developing TSVN but about how to
use it. So the users list is the one you have to ask the question.
second: why do you need information about the mergeinfo properties?
Users do not have to deal with those, because they're used internally
by the svn lib and should get modified by users manually. If you need
information about those, you have to ask on the Subversion mailing
list since that affects the internals of the svn library.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2696059
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-01-05 13:15:23 CET

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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