Re: checking out multiple branches of a project

[Doug Lee]

On Thu, Apr 21, 2005 at 09:20:04AM -0400, Jim.Hyslop wrote:
> Chris Cheshire wrote:
> > I have a project in source control called mylib (for example) that 
> > contains libraries used for my various programs. Currently I need to 
> > make some changes to a development branch, as well as some changes to 
> > the head. I have been deleting one, checking out the other, 
> > deleting it, 
> > checking out the original one again constantly, and it is starting to 
> > get annoying. Is there any way I can check it out so that the 
> > structure 
> > looks something like :
> > 
> > ~/src/mylib/HEAD/...
> > ~/src/mylib/dev-branch/...
> 
> Sure, piece of cake. Check out [sic] the -d option to the checkout command.

I have often wished for an automatic way to check out all existing
branches of a given module with one command.  Example:  If I have
module mymod with HEAD and branches named rel1 and rel2:

mkdir cvs_co
cd cvs_co
cvs co -b mymod
cd mymod
ls  # would list HEAD (or head), rel1, and rel2, and probably CVS)

The -b option is of course ficticious.
> 
> -- 
> Jim Hyslop
> Senior Software Designer
> Leitch Technology International Inc. ( http://www.leitch.com )
> Columnist, C/C++ Users Journal ( http://www.cuj.com/experts )

-- 
Doug Lee           address@hidden        http://www.dlee.org
BART Group         address@hidden   http://www.bartsite.com
Freedom is not the ability to have what we want.  Freedom is merely the
ability to seek it.  To be free defines what we can do, not what we can get.
(03/28/05)