Re: [C 21.4] Re: potential syntax error fix
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
COMMIT 21.4
I'm going to be better about notification of commits to 21.4.
Please note that release-21-4 (the branch tag) points to the most
recent release, not the most recent commits. These commits will all
suddenly appear at the next release. If you want to see the current
state of the 21.4 code, use the candidate-21-4 branch tag.
I haven't seen this commit come through on my candidate-21-4 tagged
tree. Is there something wrong with my setup?
Here are the only differences I'm currently seeing between my trees
based on the release-21-4 and candidate-21-4 tags:
diff -q -r xemacs-21.4-release/ xemacs-21.4/ | grep -v /CVS/
Only in xemacs-21.4/: CHANGES-msw
Only in xemacs-21.4/: build-msw-release.sh
BTW, I personally don't see the benefit of the candidate-21-4 tag.
From my point of view, if someone wants the latest released code, they
can ask for it by name. Especially on the (nearly) stable branch, the
latest code should be the greatest code. Therefore, I think
release-21-4 should always deliver the most recent 21.4 code.
My $.02.
- vin