Re: How does tag r21-5-latest-beta work?

|--==> "APA" == Adrian Aichner <adrian(a)xemacs.org&gt; writes: APA> But how does the r21-5-latest-beta tag work anyway? It is just a moving "sticky" tag. APA> How is it updated By yours truly. :-) Usually after my 6th or 7th coffee for the day I might say "lets release a beta, just for kicks..."[1]. After I've cleaned up my workspace and committed the ChangeLogs, CHANGES.beta, version.sh etc, I'll tag the tree. First: cvs tag r21-5-x Then: cvs tag -F r21-5-latest-beta All the magic is in the '-F'. It 'F'orces files to be tagged with this tag even if a previous version of the file already has a tag of the same name.[2] Because it is "sticky" if you do a 'cvs up' in a working directory that was checked out with 'cvs co -r r21-5-latest-beta xemacs', nothing will get updated in your working directory until I move the tag ('cvs tag -F...') to the next release. Is that nifty or what? :-) APA> and where does it point to (latest sources or latest APA> beta release sources)? Latest beta release sources. In other words, the contents of 'xemacs-21.5.10.tar.gz' on ftp.xemacs.org is more or less identical to what the current r21-5-latest-beta tag points to in CVS. Does that clear it up for you, Adrian? If not, just yell. Footnotes: [1] For those who are worried, I don't make the decision that way, normally I wait until the 10th coffee. :-) [2] Files in CVS can only have unique tag names. -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------&lt;youngs(a)xemacs.org&gt;---|