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
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.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-17 21:53:04 CEST