Michael Ambrus <[EMAIL PROTECTED]> wrote:
> I'm working on a subset of an bigger project and I could use a way of
> maintaining both the subset and keeping up to date with the main project
> without messing around too much with patches. Preferably from the root of
> the combined source-tree as with any normal CVS project.
If I understand correctly, all you have to do is define the subproject
in your modules file.
cvs checkout CVSROOT
cd CVSROOT
<edit the modules file>
cvs commit
In the modules file, you make up names for your projects and give
the path to the top of their tree (relative to $CVSROOT). There is
no reason a project can't point to a subtree of an enclosing project.
mainproject path/to/top
subproject path/to/top/and/thence/to/sub
You can then check out 'subproject' by itself. Hopefully it is
self-contained so you can build and test it standalone. Any commits
you make to your subproject/ sandbox will show up when you update
your mainproject/ sandbox, and vice-versa.
If this isn't what you want, please clarify.
--
pa at panix dot com
_______________________________________________
info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs
