1:04 p.m.
I vaguely remember Steve saying that the tag for 21.2 had changed, or
something. Can somebody tell me what's the status of the following information
(particularily which stuff is obsolete), and what I should do to update ?
Thanks.
CVS/Repository: /usr/CVSroot/XEmacs/xemacs-20
CVS/Root: :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot
CVS/Tag: Trelease-21-2
--
/ / _ _ Didier Verna http://www.inf.enst.fr/~verna/
- / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr
/_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46
75634 Paris cedex 13 Fax. (33) 01 45 81 31 19
2:13 p.m.
On Tue, Dec 08, 1998 at 02:04:50PM +0100, Didier Verna wrote:
I vaguely remember Steve saying that the tag for 21.2 had changed,
or
something. Can somebody tell me what's the status of the following information
(particularily which stuff is obsolete), and what I should do to update ?
Thanks.
CVS/Repository: /usr/CVSroot/XEmacs/xemacs-20
CVS/Root: :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot
CVS/Tag: Trelease-21-2
This is ok.
A good way to make a reality check in this area is to use
http://cvs.xemacs.org and look at a frequently modified file.
Changelog is good for that.
http://cvs.xemacs.org/cgi-bin/cvswebx/xemacs-20/ChangeLog:
You can see:
CVS Tags: r21-0-59, HEAD
CVS Tags: r21-0-58
CVS Tags: r21-2-5; Branch: release-21-2
CVS Tags: r21-2-4, r21-2b4; Branch: release-21-2
CVS Tags: r21-2b3; Branch: release-21-2
CVS Tags: r21-0-57, r21-0b57
CVS Tags: r21-2b2; Branch: release-21-2
CVS Tags: r21-0b56
This means:
- the 21.2 versions are still on the release-21-2 branch
- the change was from 21-xby to 21-x-y for the individual release
tags, which you don't use
OG.
5:46 p.m.
Olivier,
I found your advice a little obscure, but it's probably just that
I'm not that comfortable with the CVS terminology.
galibert(a)pobox.com said:
This means: - the 21.2 versions are still on the release-21-2 branch
-
the change was from 21-xby to 21-x-y for the individual release
tags, which you don't use
Over the weekend I got the 21.0 sources from CVS for the first time, but I
couldn't figure out how to get 21.2; then last night for the first time
I managed to get 21.2 sources from CVS. I used the command:
'cvs update -r r21-2-5 xemacs' (IIRC).
I guess the project is 'xemacs' regardless of whether I care about 21.0 or
21.2, right? As patches are checked in, but before r21-2-6 is created,
what tag/release will get me the latest bleeding edge sources? Was the
'Trelease-21-2' which you quoted in your message a typo? Should it
actually be 'release-21-2'?
thanks,
vin
7:52 p.m.
On Tue, Dec 08, 1998 at 12:46:41PM -0500, Vin Shelton wrote:
Over the weekend I got the 21.0 sources from CVS for the first time,
but I
couldn't figure out how to get 21.2; then last night for the first time
I managed to get 21.2 sources from CVS. I used the command:
'cvs update -r r21-2-5 xemacs' (IIRC).
I guess the project is 'xemacs' regardless of whether I care about 21.0 or
21.2, right? As patches are checked in, but before r21-2-6 is created,
what tag/release will get me the latest bleeding edge sources? Was the
'Trelease-21-2' which you quoted in your message a typo? Should it
actually be 'release-21-2'?
There are two main marking concepts in cvs: tags and branches.
Tags mark one particular release, like the 21.2.5 one. Steve now
builds them with the r21-[minor]-[beta] naming structure. So "cvs
update -rr21-2-5" will always get you the 21.2.5 version, "cvs diff
-rr21-2-5" will diff with the 21.2.5 version.
Branches mark the last version of a particular group of releases. We
use the branch called "release-21-2" for the 21.2 series. So "cvs
update -rrelease-21-2" will always get you the latest 21.2 release
(21.2.5 now, 21.2.6 later, etc...).
There is an unnamed default branch. It is the one you get when you
don't put a -r option at all. In the cvs jargon, it is called the
trunk. For us, it holds the 21.0 series.
When you use the "-rxxx" option to "cvs update", it is sticky.
This
means, each subsequent time you do a parameterless "cvs update", the
"-rxxx" is implicitely added. If you want to have it removed, and
hence get the truck back, use "cvs update -A".
The "Trelease-21-2" was the content of the "Tag" file of the
"CVS"
directory, which holds said sticky reference. The "T" isn't a typo,
but a prefix. CVS' own internal mess.
Here it is, hope this helps.
OG.
4:07 p.m.
Olivier,
Yes, thanks for your help. -rrelease-21-2 did the trick for me.
Perhaps you would like to cons up an example for the cvs.xemacs.org website?
The stuff that's there now is a good cookbook for 21.0, but it doesn't
really help with the 21.2 branch.
Thanks for your help,
vin
galibert(a)pobox.com said:
There are two main marking concepts in cvs: tags and branches.
Tags mark one particular release, like the 21.2.5 one. Steve now
builds them with the r21-[minor]-[beta] naming structure. So "cvs
update -rr21-2-5" will always get you the 21.2.5 version, "cvs diff
-rr21-2-5" will diff with the 21.2.5 version.
Branches mark the last version of a particular group of releases.
We
use the branch called "release-21-2" for the 21.2 series. So "cvs
update -rrelease-21-2" will always get you the latest 21.2 release
(21.2.5 now, 21.2.6 later, etc...).
There is an unnamed default branch. It is the one you get when
you
don't put a -r option at all. In the cvs jargon, it is called the
trunk. For us, it holds the 21.0 series.
When you use the "-rxxx" option to "cvs
update", it is sticky. This
means, each subsequent time you do a parameterless "cvs update", the
"-rxxx" is implicitely added. If you want to have it removed, and
hence get the truck back, use "cvs update -A".
The "Trelease-21-2" was the content of the
"Tag" file of the "CVS"
directory, which holds said sticky reference. The "T" isn't a typo,
but a prefix. CVS' own internal mess.
Here it is, hope this helps.
9459
days inactive
9460
days old
4 comments
3 participants
participants (3)
-
Didier Verna -
Olivier Galibert -
Vin Shelton