On Wednesday 12 April 2006 09:58, Dirk wrote:
> 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

This is exactly the kind of scenario I was trying to avoid by using versioned 
properties.

> 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?

This is the question I never could answer very well when I tried thinking 
about implementing copy-to-/tags approach in the old script.

> What will happen, if we assign the same label to a file outside the
> hierarchie, for example to $/A/Readme?

Is it possible promote this file to that label?

Leo

_______________________________________________
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

Reply via email to