Mergeinfo and Upgrades of Pre-existing Repositories

 
Hello,

Suppose that I have a version of SVN prior to 1.5 and a repository
containing many branch (copy) and merge operations.

For those, there will be no mergeinfo. Hopefully, any merge operations
will have suitable details manually recorded, such as the <svn merge>
command in the commit message.

After I upgrade to version 1.5, new merge (and branch?) operations
will benefit from the presence of mergeinfo. But that won't be the
case for old branches and old merge operations.

Because of that, I have a couple of questions:

(1) Is there anything that can be done to construct mergeinfo for the
branch and merge activity that existed prior to the upgrade? This
could perhaps as part of the upgrade itself, or as a post-upgrade
step. I imagine the answer to this will essentially be "no".

[That svn:mergeinfo is a versioned property (rather than an
unversioned one) might have an effect on the answer here.]

(2) What are the guidelines for working with a repository that has
been upgraded like this, and thus in which the mergeinfo is partial?

In order to answer these questions, if you could point me towards some
good reference or tutorial material to read that would be great.

Many thanks,
Rob.

________________________________________________________________
This message has been independently scanned for the Softel Group and cleared of containing viruses and other malicious data.

Powering Television Beyond the Video (TM)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-21 11:48:51 CET