Mary Gardiner wrote:
> btw can anyone give me a run down on this situation:
>
> X outside project (say an open source project) has a cvs tree. I want to be able
> to import their CVS tree, whilst at the same time maintaining my own tree, probably
> minor, of changes, and resyncing every so often.
mkdir x-outside-project
cvs checkout -<some option> <their CVS address> <project-tree>
I'm not sure what the option is, but I maintained both Sourceforge
and Netizen CVS trees under my CVS directory by having $CVSROOT
as the Netizen one, and using the option (it's in Sourceforge's
'cvs help' page, if nothing else) when first checking out the
Sourceforge tree.
You only need it when first populating that directory, it's stored
in that directories' CVS data file.
Jenn V.
--
"Do you ever wonder if there's a whole section of geek culture
you miss out on by being a geek?" - Dancer.
[EMAIL PROTECTED] Jenn Vesperman http://www.simegen.com/~jenn/
_______________________________________________
techtalk mailing list
[EMAIL PROTECTED]
http://www.linux.org.uk/mailman/listinfo/techtalk
