Steve Williams wrote:
>We use labels extensively in VSS to simulate the functionality of branches
>in SVN. Very painful, but necessary at the moment.
>
>Note that an inherited label (a label of a parent project) outputs a history
>entry like the following...
>
>**********************
>Label: "MK Release 266"
>User: Dave Date: 2/04/04 Time: 12:02p
>Labeled
>Label comment:
>
>That was incidentally the very next entry after the one I gave earlier.
>Your Perl script seems to handle these just fine by skipping them.
> The --debug output of vss2svn prints them out as DEBUG(4).
>
>
>
We never used labels much because we were stuck at VSS database version
5 (I almost laugh as I type "VSS database"), since the Unix port of VSS
was never upgraded to version 6. So a lot of the label promotion stuff
wasn't even available for us.
And yes, anything between the "Comment:" line and the next row of
asterisks is assumed to be part of the comment, so it will all get
slurped into the checkin comment for that file or group of files.
BTW, I didn't mention this on the website, but in order to simulate
atomic commits in VSS, the script treats multiple consecutive commits
with the same date, user, and comment all as being part of the same
atomic commit when migrating into SVN.
toby
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 20 14:33:26 2004