I'm guessing from the lack of response that nobody is having to deal
with a similar environment. Does anyone at least have any theoretical
comments?
Thanks,
Tad
> -----Original Message-----
> From: Tad Marko [mailto:tad.marko@bhnetwork.com]
> Sent: Thursday, November 01, 2007 5:55 PM
> To: users@subversion.tigris.org
> Subject: Subproject organization question
>
> Howdy!
>
> I hope that someone can help me with a question that I have
> which is more of a usage or procedure question. In the past,
> I've used CVS at other companies where there was a repository
> and then a certain number of projects under the repository.
> Those who could commit to the repository could create new
> projects as needed and projects mapped more or less
> one-to-one to their Eclipse namesakes. The current company
> that I work for has made project creation something that must
> be requested of admins. Projects here contain multiple
> subprojects, so one has to dig about inside of the trunk,
> branches or tags directories looking for the actual project
> you want to check out since we have these conventional
> directories at the top of each project.
>
> I'm wondering if there is any reason why I couldn't eliminate
> those directories from the top of the project (or at least
> ignore them) and recreate them inside of each subproject, so
> that I'd have something like
>
> project-->sp1-->trunk-->[eclipse project files and code
> dirs with code]
> | |->branches-->[copies of trunk]
> | -->tags-->[copies of trunk]
> |
> |--sp2-->trunk
> |->branches
> |->tags
>
> This would allow me to view the project more like a
> repository and the teams could create "subproject" (which I
> view as projects) as needed while maintining the ability to
> tag and branch the "subprojects"
> independently of each other.
>
> Thanks for any comments.
>
> Tad
>
"Email Firewall" made the following annotations.
------------------------------------------------------------------------------
Warning:
All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately.
==============================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 5 17:42:47 2007