> -----Original Message-----
> From: Dennis Jones [mailto:djones_at_grassvalleysoftware.com]
> Sent: Tuesday, May 03, 2011 7:09 AM
> To: users_at_tortoisesvn.tigris.org
> Subject: Re: Repeated merges problem
> "Dennis Jones" <djones_at_grassvalleysoftware.com>
> wrote in message news:ipcomh$947$1_at_dough.gmane.org...
> > How can I clean up my repository so that these files/folders don't
> > wanting to be merged all the time?
> This conversation seems to have stalled. Any other ideas on this?
> Supposing that I don't care about losing the merge info, can I just
> the merge properties the files/folders that are having a problem?
> allow me to do a one-time merge that will clean everything up?
> - Dennis
You should be able to track down the problem with the information we
have supplied. The bottom line is that SVN 'remembers' what has been
merged using properties, 'svn:mergeinfo'. The value of this property is
a path in the repository and a list of revisions already merged from the
listed path to the current path. Here's an example I made up (so it may
not be 100% correct but should be close enough for you to figure out
what you're looking at.)
Say this is the property a trunk working copy. This tells you that
Subversion has merged revisions 100, 105, 106, and 107 from the featurea
branch to the trunk.
You need to look at the svn:mergeinfo stored in your working copy and
match that with the files, folders and revisions you are having problems
with and make sure that the svn:mergeinfo includes information about
those revisions. My guess is that this information is missing. If it is
not then I don't know what the problem is.
Also, I would expect this property to appear only in the root of your
project directory structure. I am sure there are reasons to do it
otherwise but I would not expect that in general. In other words you
should know what you are doing in that case.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-05-05 01:40:20 CEST