Hi,
I gave this a very fast try and came around the following question
regarding label promotion:
Let's assume, that we have a deeply nested project structure:
> $/A/B/C/D/E/File.txt
At some point in time, we label the $/A/B project with the Label
"beta-0.10" ;-)
Later, we want to promote the same label on a newer version of the file
"file.txt" so we explicitly set the label on the file.
The easy solution would be to simply copy the directory, where the label
was assigned in the first place to the tags directory into a directory
named after the label. The we would have the following structure:
> /tags/beta-0.10/C/D/E/File.txt
Later we encounter the label on the file and we can not simply copy the
file into the tags directory, since
* the tag/label already exists
* the tag/label was created from a different directory
Now the question, how do we know that we have to copy to
/tags/beta-0.10/C/D/E/File.txt, thereby overwriting the old version?
How do we know the correct relative path in the tags directory?
What will happen, if we assign the same label to a file outside the
hierarchie, for example to $/A/Readme?
Should we simply retain the complete project structure in the tags
directory, e.g.
> /tags/beta-0.10/A/B/C/D/E/File.txt
even if the label was assigned only to the "$/A/B" project?
Dirk
P.S. I still have to lookup what will happen, if you assign a label to a
file first and later to the project. I would expect, that the label
promotion feature is still active in this case.
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
