RE: How to organize a Subversion based code tree

That is exactly my problem also. I have some common files which are used intermittently by other
software components in the projects.

The projects as such are independent but due to common files (common utilities) its getting
difficult to define what would the complete repository look like.

Also, when I check out Project A, I just need the trunk not the tag or the branch folders. Is
there an automated solution for it or does it need to be done manually.

Every suggestion is welcome,
Thanks and Best regards,
Vishal Sapre

--- Joe Attardi <joeattardi@yahoo.com> wrote:

> > Do you have "common" files, and what do you do with
> them? for
> instance, a common ini file
> > or library file all three projects depend on...
>
> I must have missed that part... I don't have common
> files between the
> different projects.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

=======================================
A train station is where the train stops.
A bus station is where the bus stops.
 
On my desk, I have a work station... !!
 
  

                
__________________________________
Discover Yahoo!
Stay in touch with email, IM, photo sharing and more. Check it out!
http://discover.yahoo.com/stayintouch.html

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 2 23:19:02 2005