I think:
Check out the trunk and each branch. For each run "svn pd svn:mergeinfo .
-R" and then commit.
On Wed, Mar 25, 2009 at 2:09 PM, Chris Lajoie <ctlajoie_at_gmail.com> wrote:
> When 1.5 came out, I got a little too excited and updated our server
> immediately. I had been using svnmerge.py for merge tracking, so I ran
> the migration script, and everything appeared to work as intended.
> However, once I started using merge tracking, I started noticing some
> very odd behavior. I could go into detail about what happened, but I
> have done some googling and I believe I have a very vague
> understanding of why these things happened. If I understand correctly,
> the issues I am having are a result of mergeinfo props on past
> revisions of directories that no longer exist in HEAD (or are named
> something different in HEAD) and the svnmerge migration tool was
> unable to account for all the structure changes our repository has
> gone through.
>
> I would like to start fresh -- remove all of the svn:mergeinfo props
> from all revisions. Is there a way to do this?
>
> Chris
>
> ------------------------------------------------------
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1418378
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe_at_subversion.tigris.org].
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1418821
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-25 20:01:48 CET