Re: CVS (slightly off-topic)

[Adam Spiers <adam@thelonious.new.ox.ac.uk>]

Peter Stephenson (pws@ifh.de) wrote:
> As far as organizing a CVS archive goes, we could arrange it so that,
> for example, Sven made changes to the completion code, and I did it
> for the rest, or Bart did in the case of my absence or total
> incapacity due to huge volume of patches.  Changes wouldn't appear in
> the archive until after they'd been seen on the list --- though at the
> present rate of change, how much after is difficult to judge.

On the subject of CVS, I've been trying to get my head around (vendor)
branches and have been wondering what the best strategy would be for
using CVS to track changes.  I know that several of you are already
doing this; would you mind briefly detailing what strategy you use?
In particular, do you use a vendor branch?  Several, even?  Do you
make your own changes to the main branch, or to a branch of your own?

It also struck me that even if an official anonymous CVS facility were
to be set up, this still wouldn't be a complete solution (correct me
if I'm wrong) for anyone who wanted to actively develop, since to
develop you ideally need your own repository.  If you wanted to merge
in changes from the anon CVS to your own repository, would you have to
update your working copy of the anon CVS and then `cvs import' your
working copy into your own development repository, or is there a
better way?

Apologies for the off-topicness, but once I get this sorted I'll find
it much easier to contribute (cvs rdiff with tags is a real joy).

Adam