Erik Moeller wrote:
CVS code (the default). In that case, it will first
have to be merged into
the stable branch. This might take a while given that there's still some
incomplete stuff (category code, new interlanguage links code) in the
unstable branch. If Magnus doesn't finish these soon, I will probably
remove them entirely.
If you want your code to go live with the next update cycle, you should
commit it to stable immediately (but be sure it doesn't break anything).
Just switch your working copy to stable, or check out a separate working
copy from that branch, and commit it there.
See
http://www.loria.fr/~molli/cvs/doc/cvs_5.html
for details.
eep.
I use WinCVS, which isn't the most helpful of itnerfaces.
AFAIK I had commited Ro to the stable branch, since the revision number
I as given was 1.1 once the action was complete.
I can work out how to branch a particular module or file, but nothing
about switching.
I think I had best keep away from CVS, as I have trouble visualizing
what these things mean.