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

Let me add some labels so we can be more precise
[trunk below my new way]
/bbook/fnfapp/trunk
/bbook/fnfapp/branches
/bbook/fnfapp/tags
/bbook/fnflib/trunk
/bbook/fnflib/branches
/bbook/fnflib/tags

 and

[trunk above the usual redbean way]

/bbook/trunk/fnfapp/
/bbook/trunk/fnflib/
/bbook/tags/fnfapp/
/bbook/branches/fnfapp/

> This way you can branch the fnflib without branching fnapp.

What is the specific reference to "this" the [trunk below] or
[trunk above]

I'm not seeing which you are referencing, and can't tell which is true.

From what I can tell, "tags" are really not important or defined to SVN,
they are just directories, its the users who layer meaning on top of the
structure. So it looks to be a six of one, half dozen of the other to me.

Same with branches, they are a usage convention, nothing more.

Or am I missing something here?

> also tag each project individually. While, you can still in theory do
> it with the second layout... the first layout makes much more sense
> if you have many projects in a single repository.

I don't see any difference, or don't understand them. so I'm not seeing
the "much more sense" that you write about.

>> Having the [trunk below] always struck me as making them
>> more visible.
>
> They are just as visible the first way above.

Depends, or perhaps it is all a wash. I'm struggling to understand this.

Thanks

-- 
Pat Farrell
http://www.pfarrell.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2393040
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].