Thanks everyone for your insight!
Related to this, I have a question regarding the
organizational structure of CVS. I noticed that
cvs.apache.org has, predictably, a different package
for all of the top-level projects, and even
sub-projects (although all of the commons-components
are considered components and not sub-projects, hence
the lack of any of the components at this top level).
I also noticed that each of the websites is listed as
[projectname]-site.
I'm certainly not the worlds foremost expert at CVS,
so I naturally assume that since apache is laid out
this way that this must a great way to lay out a
project & its sub-projects in CVS. Is this so? What
are the pros/cons to doing it this way, as opposed to
a true tree structure? I assume it has something to do
with the way CVS does things.
Thanks again
Richard
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - What will yours do?
http://my.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
