Hi
I have a CVSROOT tree structure like this:
/cvsroot
|
---business1_module1
|
---business1_module2
|
---business1_module3
.
.
|
---business2_module1
|
---business2_module2
|
---business2_module3
Certain new modules have come up for development which are logically a part of the existing ones, but would be developed independently.
My first question: Should I create a separate module altogether? (like business1_module1_1 .... )
If I plan to create it *inside* business1_module1(so that I don't clutter up /cvsroot with 100's of projects) , I would have to make changes to the 'modules' file. I did this:
business1_module1_1 -d business1_module1/business1_module1_1
business1_module1 -d !business1_module1/business1_module1_1 business1_module1
However, when I do a checkout of business1_module1_1, the sandbox first has the subdirectory business1_module1.
Question: How do I have business1_module1_1 as the 'root' module directory on my sandbox?
Finally, is there any set of guidelines that a CVS administrator should follow on the repository hierarchy when a large number of projects/sub-projects exist?
TIA !
---
Mohit
DISCLAIMER: The information contained in this message is intended only and solely for the addressed individual or entity indicated in this message and for the exclusive use of the said addressed individual or entity indicated in this message (or responsible for delivery of the message to such person) and may contain legally privileged and confidential information belonging to Tata Consultancy Services. It must not be printed, read, copied, disclosed, forwarded, distributed or used (in whatsoever manner) by any person other than the addressee. Unauthorized use, disclosure or copying is strictly prohibited and may constitute unlawful act and can possibly attract legal action, civil and/or criminal. The contents of this message need not necessarily reflect or endorse the views of Tata Consultancy Services on any subject matter. Any action taken or omitted to be taken based on this message is entirely at your risk and neither the originator of this message nor Tata Consultancy Services takes any responsibility or liability towards the same. Opinions, conclusions and any other information contained in this message that do not relate to the official business of Tata Consultancy Services shall be understood as neither given nor endorsed by Tata Consultancy Services or any affiliate of Tata Consultancy Services. If you have received this message in error, you should destroy this message and may please notify the sender by e-mail. Thank you.
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
