Re: Gnus v5.10.5 is released

[Steinar Bang <sb@dod.no>]

>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:

> Steinar Bang <sb@dod.no> writes:
>> As long as a release is tagged, you can put a branch tag there
>> anytime.

>> Eg.
>> 	cvs rtag -b -r v5-10-5 b5-10-5 gnus
>> (or something like that)

> Right.  I've never actually branched anywhere using cvs...  :-)

If you don't plan to merge the branch back in, it isn't really hard.

 - with a command like the above you place a branch tag at the point
   where you would like the branch to start.  As for naming the branch
   tags, in the example above, I've given the branch tag the same name
   as the version tag at its root, but with the "v" replaced with a
   "b"

 - then check out a separate Gnus CVS workspace on the branch, eg.:
	cd /tmp/
	cvs co gnus
	cvs up -dP -r b5-10-5
	mv /tmp/gnus ~/cvs/gnus-5.10-branch

All commits you make in this workspace (including adds and removes)
will be on the branch.  What you'll see on updates is commits other
maintainers have made on the branch.  Files that have been removed in
the trunk after the branch, will still be present, editable and
commitable on the branch.