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

Re: looking for one word to encompass trunk, tag and branch

From: Hari Kodungallur <hkodungallur_at_gmail.com>
Date: Mon, 17 Aug 2009 15:14:01 -0700

On Mon, Aug 17, 2009 at 12:52 PM, B. Smith-Mannschott <bsmith.occs_at_gmail.com
> wrote:

> Good naming, they tell us programmers, is important.
>
> Trunks, tags and branches are all pretty much the same thing in
> subversion. The trunk is just a specially named branch not located in
> the branches folder. Tags are just branches that don't get edited. And
> even branches are just a convention.
>
> I'm writing some scripts to automate certain repetitive subversion
> tasks and am trying to come up with a term to encompass trunk, tag or
> branch. For example:
>
> svn://foo/trunk/a/b/c -- is some folder inside the trunk. The trunk is
> at svn://foo/trunk
> svn://foo/branches/1.x/a/b/c -- the branch is at svn://foo/branches/1.x
> svn://foo/tags/1.0/a/b/c -- the tag is at svn://foo/tags/1.0
>
> I'd like to be able, in all three cases to say the *mumble* of <url>
> is at <shorter-url>.
>
> What should I use in place of *mumble*? Things I've considered.
>
> - TTB: a three-letterism for Trunk, Tag, Branch
> - Copyto: a play on copyfrom(-url, -rev), but this seems to much
> implementation not enough conceptual.
> - Branch: but how to distinguish the all-encompassing branch from the
> specific? Very overloaded.
> - Stream: considering each as a stream of changes (ok, the tag is
> pretty dry, ...). I've seen this used in the context of other version
> control systems, so maybe this term is overloaded.
> - Fork: This term is certainly overloaded.
> - Prong: A play on fork.
> - Furcate: a nouning of an ancient adjective related to 'fork'.
>
> I'm not happy with any of these options and open to any suggestions.
> Clever, evocative and humorous ideas get bonus points.
>
>

Who exactly is the audience for this? I mean, what are you trying to convey
and to whom?

Typically the trunk/branch/tag usage is specific to a product or project.
And that usage is limited to those who use the version control system.

For example, for the svn project one might say: svn's trunk is at
http://svn.collab.net/repos/svn/trunk/
Or: the 1.6 release of svn is at:
http://svn.collab.net/repos/svn/branches/1.6.x/

In this case (and most other typical cases, I believe) the all encompassing
word is the name of the product.

PS: I am sorry, I am not able to come up with a generic term
(humorous/clever/evocative or otherwise).

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384549

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-18 00:14:51 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.