Re: cvs access for XEmacs 21.2.*

Hm, I sent off the wrong mail.. sorry about that. I started with the (incomplete!) one that I just now found in incoming mailbox, but I realised I didn't know enough about what was wanted so I wrote another one and meant to keep the first one as a draft for a later follow-up :-) Oh well. *Here's* the one I meant to send! Please disregard the first one for now (I shouldn't send emails after midnight I guess): - Tor On May 16, 3:08, SL Baur wrote: I have, on a couple of occations. It's a bit hairy. I can write up a step-by-step procedure if you want, but it would be easier if we first agree on exactly how we want the end result to be. To me it looks like the following release- and branch-tags may be particularly interesting: r21-1-2 (revision: 1.195) (latest on trunk) release-22-0 (branch: 1.155.4) (a branch) release-21-2 (branch: 1.155.2) (a branch) r20-0patches (branch: 1.12.2) (a branch) Do you want what is now the 21-2 branch to be on the (development) main trunk, and what's currently (21-1-2) on the main trunk to be a 21-1 (stable) branch? And let the others be as they are (r20-0patches a stable branch, 22-0 a development branch)? Or something else? There are a couple of methods to do these things, however they all involve creating new branches. Unfortunately the trunk (aka main branch) doesn't have a name in CVS, and unfortunately there's no functionality[1] in CVS to assist much in renaming. So some tagging and branching and copying will have to be done. -Tor --- Footnotes: [1] There is a mechanism to give another name to a branch, unfortunately it's extremely buggy and can't be used. If the main branch hadn't been anonymous this (non-working) functionality could have made this renaming process quite easy. But that's not to be :-)