Mike,
This is a subversion issue; it's not restricted to TSVN, and so this
isn't really the place to get answers about it. This topic has been
covered many times on the subversion users mailing list, so I'm not
surprised there haven't been more responses to this thread.
Still -
Most of the excessive mergeinfo is only created when using svn
1.5.0-1.5.5, and it happens any time you do a repo-to-repo copy. (This
naturally also happens if you rename or move a file, since those
operations are performed with a copy+delete.)
1.5.6 and later (including 1.6.x) don't generate as much new
mergeinfo. However, this does nothing for the mergeinfo that you have
already committed to your repository. This is why you're still seeing
mergeinfo changing when you go to commit a merge; all of the existing
mergeinfo properties have to be updated, even if no new ones are being
created.
If you revert the mergeinfo changes instead of committing them, then the
stored information about merging will be wrong. This means that anything
that relies on the mergeinfo will be relying on wrong information and
may do the wrong thing.
Paul Burba wrote an excellent in-depth article about mergeinfo if you
want to better understand what's going on. You can find that here:
http://www.collab.net/community/subversion/articles/merge-info.html
Ahhhh... that's what I was looking for. Thanks a lot for clarification.
--Heiko
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2325676
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-05-20 08:25:20 CEST