Martin Buchholz <martin(a)xemacs.org> writes in xemacs-beta(a)xemacs.org:
>>>>> "Peter" == Peter Bernard West
Peter> Martin Buchholz writes:
>> The officially sanctioned way to get 21.2 via CVS is:
>> cvs -z3 -d :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot checkout -R release-21-2
>> I changed the tag as well so that a simple `cvs update' will get the
>> latest CVS sources.
This better not mean what I think it means.
Peter> Does this mean that if I `cvs update' in an xemacs directory
Peter> containing the 21.0.6 cvs sources, that they will be updated to the
Peter> 21.2.8 (or whatever the current head of the branch is) sources?
The release branch tag is sticky. Once you check out a branch, you
can do `cvs update's in it to get updated versions.
No. It will be updated to the latest 21.0 sources.
Peter> If I want to track the 21.0 sources, must I `cvs update -R
Peter> release-21-0' in said directory? ...
If you wish to track both versions use two XEmacs source trees. Check
out one with the default branch, eg. something like
cvs -d :ext:steveb＠cvs.xemacs.org:/usr/CVSroot checkout xemacs -d xemacs-21.0
for the 21.0 (and soon-to-be) 21.1 sources.
cvs -d :ext:steveb＠cvs.xemacs.org:/usr/CVSroot checkout \
-rrelease-21-2 xemacs -d xemacs-21.2
for the experimental 21.2 sources. This sequence will use the
subdirectory xemacs-21.0/ to store the stable version and xemacs-21.2
to store the experimental version. You should then be able to run
`cvs update' in each top-level XEmacs source directory to get future
I haven't tried that, but I think it should work. Check the
version.sh file after your `cvs update' to make sure you got the
version you expected.