Re: [for 20.2] ~user completion
[xemacs-beta cc restored]
This is all new ground to me. Please correct me if I got any of this
wrong.
Greg Klanderman <greg(a)alphatech.com> writes:
Hi Steve,
I'd like to send an update to the patch referred to below
reflecting
discussion with Ben and adding documentation. In your 21.0-pre10
announcement, you mention:
> Note also that the 21.2 CVS tree was synched with these changes
and is
> now at 21.2-beta2-pre3.
I just performed the checkout command:
$ cvs -d :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot checkout \
-rrelease-21-2 -d XEmacs-21.2 xemacs-20
and got the latest version with the src/dired.c boo-boo.
I believe the trick is to use the branch tag `release-21-2' instead of
a specific beta tag.
Once a tree is checked out, `cvs update -d' should always get the
latest and greatest revision on that branch.
and you also say below that my patch is applied. I'm not sure
what
tag however is the current 21.2. Doing `cvs log src/dired.c' gives
the following symbolic names containing 21-2:
r21-2b1: 1.18
release-21-2: 1.18.0.2
My understanding was that release-21-2 was the split and that
r21-2bN
would be betas from there.
That is correct.
(Bear with me I've not used branches yet).
No problem. I am not comfortable with branches yet either.
Anyway, I would have expected a r21-2b2, but it is not there.
I haven't made a 21.2-beta2 yet. The r21-2b2 tag won't be created
until the beta is formally made. This is consistent with how I've
managed the 21.0 beta series.
Furthermore, r21-2b1 is version 1.18, same as the current 21.0, and
thus does not have my patch applied.
That is correct.
Only release-21-2 has the patch applied. Am I just confused, or is
there a problem here? Or have you moved the release-21-2 tag forward
as you synch with 21.0? Hmm maybe that's it.
That appears to be a feature. It is consistent. If you don't specify
a release tag, you get the latest revision from the default branch.
If you specify a branch tag, you get the latest revision from that
branch.