Hi again, I've just been informed that this mechanism *is not* supported in non-EVS versions of CVSNT. Specifically, the deletion of branch tags, in particular when at least one alias tag is present, is not supported.
I wanted to get back to the list regarding this since this mechanism appeared to be supported (as well as recommended) in previous non-EVS versions of CVSNT (see, for e.g., http://www.cvsnt.org/pipermail/cvsnt/2005-March/017696.html) and it may be that others have been using/attempting this. Regards, -David > Hi there, > > Before I start using alias tags (with 2.5.03) for the purposes of renaming > branch tags (alias tags being what appear > to be the preferred mechanism for this) I had a question I wanted to run by > the list. In our use case we'd like to > actually re-use the old (renamed) branch tag to reference a new branch. > > My question: is this problematic for pre-existing sandboxes that reference > this "old" branch tag, or will the > subsequent (i.e., post-rename, post branch tag re-create) update simply > update the sandbox with the new branch tag's > location information? I would think this would be the case, but I wasn't sure > about some of the explicit revision > numbers that are present in the CVS/Entries file... > > Thanks in advance for any help, > -David Hauck > _______________________________________________ > cvsnt mailing list > [email protected] > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt > > Upgrade to CVS Suite for more features and support: > http://march-hare.com/cvsnt/ _______________________________________________ cvsnt mailing list [email protected] http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
