[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Subclipse-users] Best practice - Trunks and Branches

From: Hughes, James <jhughes_at_linx.co.uk>
Date: Fri, 4 Jan 2008 17:36:29 +0100

Hello all,

Hope this is the right place to post this - we use Subclipse!

Our repository does not currently have and trunks or branches, but we
need to start using them for multiple dev paths. However, after reading
the Subversion docs on this they suggest something like the following...

Repos/some-library/trunk
Repos/some-library/branches
Repos/some-other-library/trunk
Repos/some-other-library/branches/china
Repos/some-other-library/branches/japan

Etc etc for however many libs and application you may have in the
repository.

However, my brain seems to want to do it this way...

Repos/trunk/some-library
Repos/trunk/some-other-library
Repos/branches/china/some-library
Repos/branches/china/some-other-library
Repos/branches/japan/some-library
Repos/branches/japan/some-other-library

i.e. You only have one trunk folder and one parent branches folder
rather than having them underneath each sub-part of the project.

What do people suggest and why?

James

This message (including any attachments) contains confidential
and/or proprietary information intended only for the addressee.
Any unauthorized disclosure, copying, distribution or reliance on
the contents of this information is strictly prohibited and may
constitute a violation of law. If you are not the intended
recipient, please notify the sender immediately by responding to
this e-mail, and delete the message from your system. If you
have any questions about this e-mail please notify the sender
immediately.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-01-04 17:37:13 CET

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.