Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
It's also somewhat disconcerting that rtag gives no response whatsoever . . I've become deeply atached to cvs -q's output - especially on tagging. . . But, your cvs tag -l requires tha tthe entire repository be checked out locally, and that's what I"m trying to avoid. I'd like to hear the awsner to Keith's question as well. >>> "keith d. zimmerman" <lists at kdz13.net> 7/22/2004 9:27:49 AM >>> Aaron Kynaston wrote: > I'd like to find a good way to tag an entire repository (all files on > the main head) besides checking out the entire thing and then tagging? > > Our repository is getting somewhat unwieldy (9 - 11 gb depending on the > day :-) ) and I'd like a way to tag it more easily. Andreas Tscharner wrote: > Aaron Kynaston wrote: > >> Wow - thanks for the quick reply. >> >> How do I refer to the latest running non-branch version? I thought it >> was HEAD but that didn't seem to work . . > > > Don't use a name at all. That should work. > Besides: rtag does exactly what you want: It tags the current module in > the repository even if someone is committiing his/her changes while you > were tagging (Gives some inconsistency...) > Terry Lacy wrote: > > Nearly forgot, if you use the rtag command, you'll want to > save yourself a lot of pain and suffering by locking out > other users while the repository is being tagged. Otherwise, > you'll end up with partial check-ins. > This is interesting. First of all, i re-sign up for the mailing list because i wanted to ask this very question. Secondly it is interesting because the thread forked, and two different answers were given on the different threads. So, my questions.... The way we were doing things was to run rtag on the top of the sandbox at the time that we ran our build script. But since our repository is so large this could take a *long* time. Users were complaining about getting lock errors, etc, etc. So we changed the script. We now run 'tag -l' recursivly through the entire tree. This eliminates the lock errors.... but takes *forever* (ok, only an hour or so, but....) This also results in a guarantee that what was built is what was tagged (I have the files already checked out for the bulid, so tag works just as good, if not better, than rtag) So, how do other people deal with this? Do you lock your users out while building? Also, can somebody answer concretely the discrepancy in the two threads. My experience has been that everybody is locked out while tagging, but i could be wrong. And speeed..... why does this take so long? thanks, -kz _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs