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

Re: best way to add /trunk /tag /branch to existing repository

From: B. Smith-Mannschott <bsmith.occs_at_gmail.com>
Date: Wed, 9 Sep 2009 08:27:15 +0200

On Wed, Sep 9, 2009 at 01:23, Pat Farrell<pfarrell_at_pfarrell.com> wrote:
> I'm sure that there is an easy way to do this, but I can't find it in
> the RedBean...
> I have a project under SVN that does not have the usual three paths for
> /trunk and /branch and /tag
> When I started it, it was just me, so there was no need for tags or
> branches.
> The project is getting bigger, and I'd like to put the usual three in.
> So if I look at the top of the tree today, I see
> repos - Revision 3346: /bbook
>    * ..
>    * docs/
>    * fnfapp/
>    * fnflib/
>    * mockups/
>    * site/
>    * sql/
> What I'd like to see is something like:
>    * docs/
> /bbook/trunk/fnfapp/
> /bbook/tags/fnfapp/
> /bbook/branches/fnfapp/
> /bbook/trunk/fnflib/
> /bbook/tags/fnflib/
> /bbook/branches/fnflib/
>    * site/
>    * sql/

I'd like to offer a few suggestions for a saner layout. I can't
promise that you'll think it saner, but it's worked well enough for

(0) I've found it very helpful to have a policy of always
tagging/branching an entire codeline (trunk, tag, branch).

(1) I see that fnfapp and fnflib share a trunk, so perhaps you expect
fnfapp and fnflib to be so closely linked that they are always
released together, and share a version number. In that case, you don't
need to subdivide your branches and tags directories, since you can
always tag/branch the whole code line.


(2) If fnfapp and fnfllib are in fact separate modules (which seems
more likely) with their own releases, bug fixes and the like, the I
think it would make more sense to give each in its own tree with its
own trunk/tags/branches. In this way, they can be branched/tagged


(3) There are subversion clients that build on the subversion
tag/branch conventions (Subversive, and git-svn come to mind though
there are probably others). You'll find they work better if you hew
close to the layout conventions described in the Subversion book.

// Ben


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-09 08:28:29 CEST

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

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