You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "B. Smith-Mannschott" <bs...@gmail.com> on 2009/08/17 19:52:04 UTC
looking for one word to encompass trunk, tag and branch
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.
thanks,
// Ben
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384505
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch_53201
Posted by "Ignacio G. T." <ig...@nucleocc.com>.
El 17 Aug 2009 a las 21:52, B. Smith-Mannschott escribió:
> ... Trunks, tags and branches are all pretty much the same thing in
> subversion...
>
> What should I use in place of *mumble*?
roofolder (kind of abbreviation for "root of folders")
Or just roof (or rooftop) but I prefer roofolder. Or, for Spanish
speakers like me, "rufo", which is the Spanish name for "Rufus",
and sounds pretty funny ("Vaya, ya he vuelto a cargarme el
rufo").
Sorry for the late response, I've been on holidays :-)
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390141
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by Michael Rohan <mr...@stonepillar.com>.
Hi Folks,
Given the layout in Subversion, perhaps, calling them "meta-directories"
would work.
Take care,
Michael.
On Tue, Aug 18, 2009 at 8:53 AM, Les Mikesell <le...@gmail.com> wrote:
> B. Smith-Mannschott wrote:
> > On Tue, Aug 18, 2009 at 16:51, Les Mikesell<le...@gmail.com>
> wrote:
> >> They are all revisions... Tags are the only things that are different,
> and
> >> only by the convention that you don't commit after creating them so they
> >> only have the HEAD revision - and that isn't enforced.
> >
> > No, in the vocabulary of Subversion a "revision" is one of the
> > numbered transactions that make up the global history of a repository.
> > I have no desire to overload that term with an unrelated meaning.
>
> But they are all numbered transactions. There is no way to get anything
> else out of the repository. Perhaps the fact that the latest (head)
> transaction is conveniently used as the default if you don't supply one
> is confusing you. But find it's number and ask with/without and you'll
> see that you get the same thing.
>
> > A branch is not a revision. Nor a tag. Nor a trunk.
>
> The only thing you can reference with them is a revision. They exist
> only to hold revisions.
>
> > A branch may have
> > *been created* as part of a particular revision, when it was copied
> > form some-path last modified as part of some-other-revision. The
> > branch may even be said to have *been modified* as part of
> > this-revision and that-revision; last modified in another-revision.
>
> Try to describe how you get something other than a revision out. Or how
> committing creates something other than a revision. If you can, I've
> been missing something. (I suppose there are the non-versioned
> properties, but that's pretty esoteric.)
>
> > In our case "Version" and "revision" are both too overloaded for this
> > task. Version, in our usage, generally indicates a SCM version, like
> > 1.2.3 or 5.0.0-SNAPSHOT. We use Revision exclusively to describe
> > ordered commits to an Subversion repository.
>
> There's an elegant simplicity here. It's revisions all the way down.
>
> > Also, if we decided to call this a "revision" (url):
> >
> > svn://example.com/svn/repo/project/branches/new-hotness
> >
> > Then, what might we call this:
> >
> > svn://example.com/svn/repo/project/branches/new-hotness@r1111
> >
> > A revision revision? The "revision" new-hotness at revision 1111?
>
> Note that if your repository is at revision 1111 or there is nothing
> newer on that path, both of those refer to exactly the same thing.
>
> > As an aside, your mention of "HEAD" reminded me of something. In the
> > Mercurial world the term that I'm groping for would be "head". In
> > mercurial a head is a commit with no children, so it's the most recent
> > commit on some branch/tag/trunk. The mercurial people use the word
> > "tip" to describe the most recent head. (Roughly equivalent to
> > Subversion's use of HEAD).
>
> I think that's the elusive concept here. If you don't specify a
> revision explicitly you still get a revision that happens to be the
> HEAD. That doesn't mean it deserves another name. It's just a revision
> that, after the next commit, will require an explicit number to reproduce.
>
> --
> Les Mikesell
> lesmikesell@gmail.com
>
> ------------------------------------------------------
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384817
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe@subversion.tigris.org].
>
--
=========================
Michael Rohan
Stone Pillar Technologies
=========================
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384822
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by Les Mikesell <le...@gmail.com>.
B. Smith-Mannschott wrote:
> On Tue, Aug 18, 2009 at 16:51, Les Mikesell<le...@gmail.com> wrote:
>> They are all revisions... Tags are the only things that are different, and
>> only by the convention that you don't commit after creating them so they
>> only have the HEAD revision - and that isn't enforced.
>
> No, in the vocabulary of Subversion a "revision" is one of the
> numbered transactions that make up the global history of a repository.
> I have no desire to overload that term with an unrelated meaning.
But they are all numbered transactions. There is no way to get anything
else out of the repository. Perhaps the fact that the latest (head)
transaction is conveniently used as the default if you don't supply one
is confusing you. But find it's number and ask with/without and you'll
see that you get the same thing.
> A branch is not a revision. Nor a tag. Nor a trunk.
The only thing you can reference with them is a revision. They exist
only to hold revisions.
> A branch may have
> *been created* as part of a particular revision, when it was copied
> form some-path last modified as part of some-other-revision. The
> branch may even be said to have *been modified* as part of
> this-revision and that-revision; last modified in another-revision.
Try to describe how you get something other than a revision out. Or how
committing creates something other than a revision. If you can, I've
been missing something. (I suppose there are the non-versioned
properties, but that's pretty esoteric.)
> In our case "Version" and "revision" are both too overloaded for this
> task. Version, in our usage, generally indicates a SCM version, like
> 1.2.3 or 5.0.0-SNAPSHOT. We use Revision exclusively to describe
> ordered commits to an Subversion repository.
There's an elegant simplicity here. It's revisions all the way down.
> Also, if we decided to call this a "revision" (url):
>
> svn://example.com/svn/repo/project/branches/new-hotness
>
> Then, what might we call this:
>
> svn://example.com/svn/repo/project/branches/new-hotness@r1111
>
> A revision revision? The "revision" new-hotness at revision 1111?
Note that if your repository is at revision 1111 or there is nothing
newer on that path, both of those refer to exactly the same thing.
> As an aside, your mention of "HEAD" reminded me of something. In the
> Mercurial world the term that I'm groping for would be "head". In
> mercurial a head is a commit with no children, so it's the most recent
> commit on some branch/tag/trunk. The mercurial people use the word
> "tip" to describe the most recent head. (Roughly equivalent to
> Subversion's use of HEAD).
I think that's the elusive concept here. If you don't specify a
revision explicitly you still get a revision that happens to be the
HEAD. That doesn't mean it deserves another name. It's just a revision
that, after the next commit, will require an explicit number to reproduce.
--
Les Mikesell
lesmikesell@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384817
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by "B. Smith-Mannschott" <bs...@gmail.com>.
On Tue, Aug 18, 2009 at 16:51, Les Mikesell<le...@gmail.com> wrote:
>
> They are all revisions... Tags are the only things that are different, and
> only by the convention that you don't commit after creating them so they
> only have the HEAD revision - and that isn't enforced.
No, in the vocabulary of Subversion a "revision" is one of the
numbered transactions that make up the global history of a repository.
I have no desire to overload that term with an unrelated meaning.
A branch is not a revision. Nor a tag. Nor a trunk. A branch may have
*been created* as part of a particular revision, when it was copied
form some-path last modified as part of some-other-revision. The
branch may even be said to have *been modified* as part of
this-revision and that-revision; last modified in another-revision.
>> I like variant.
>
> Why is that better than 'revision' or 'version'? Using only one term makes
> it easier to see that there are multiple dimensions to the way you access
> them and one is as valid as another. That is, you get a revision whether or
> not you specify a revision number, and tags are just a way to tie a
> revision to the head of URL path.
In our case "Version" and "revision" are both too overloaded for this
task. Version, in our usage, generally indicates a SCM version, like
1.2.3 or 5.0.0-SNAPSHOT. We use Revision exclusively to describe
ordered commits to an Subversion repository.
Also, if we decided to call this a "revision" (url):
svn://example.com/svn/repo/project/branches/new-hotness
Then, what might we call this:
svn://example.com/svn/repo/project/branches/new-hotness@r1111
A revision revision? The "revision" new-hotness at revision 1111?
As an aside, your mention of "HEAD" reminded me of something. In the
Mercurial world the term that I'm groping for would be "head". In
mercurial a head is a commit with no children, so it's the most recent
commit on some branch/tag/trunk. The mercurial people use the word
"tip" to describe the most recent head. (Roughly equivalent to
Subversion's use of HEAD).
// Ben
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384801
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by Les Mikesell <le...@gmail.com>.
B. Smith-Mannschott wrote:
>
>> "The root of <url> is <shorter-url>."
>>
>> "The tree containing <url> is rooted at <shorter-url>."
>>
>
> Yea, actually --root is what I'd been using, though I neglected to put
> it in my list. I'm not too keen on it because it's not specific
> enough. The root of what? The project, the repository, the current
> trunk-or-branch-or-tag (tobot?)
But the 'project' is the root. It has revisions. The revisions are
located by both the URL path and revision number where the current
revision is assumed if you omit it. Why call these things anything
else? The rest is just convention as you might note by the ability to
copy any revision specified by url and revision number to any other URL
path.
>> He's not looking for a word for the project. He's looking for a word that
>> can be used to describe the trunk, or any branch, or any tag, of the
>> project.
>
> correct. In fact, let me draw a picture. (please put on your ascii-art goggles)
>
> svn://example.com/svn/repo/group/artifact/branches/ISSUE-13/src/main/java/com
> \________________________/\_____________/\_______/\_______/\______________...
> repository root url project name *mumble* *mumble* *mumble*-relative
> "repo" kind name path
> \_______________________________________/
> project url
> \________________________________________________________/
> *mumble* url
>
> Where in the case of trunk, this looks a little different:
>
> .../group/artifact/trunk/src/main/java/com
> \______/
> *mumble*
> kind &
> name
> ..._____________________/
> *mumble* url
They are all revisions... Tags are the only things that are different,
and only by the convention that you don't commit after creating them so
they only have the HEAD revision - and that isn't enforced.
> I like variant.
Why is that better than 'revision' or 'version'? Using only one term
makes it easier to see that there are multiple dimensions to the way you
access them and one is as valid as another. That is, you get a revision
whether or not you specify a revision number, and tags are just a way to
tie a revision to the head of URL path.
--
Les Mikesell
lesmikesell@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384790
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by "B. Smith-Mannschott" <bs...@gmail.com>.
Thanks for all the great replies.
On Tue, Aug 18, 2009 at 00:14, Hari Kodungallur<hk...@gmail.com> wrote:
>
> Who exactly is the audience for this? I mean, what are you trying to convey
> and to whom?
>
Audience:
- People who use the scripts I'm writing (me, a few colleagues) as i'd
use this term in an option name.
- People who maintain the scripts. (me)
i.e. Developers, though it'd be handy to have a all-inclusive term
non-technical could use in conversation with us once they'd learned
it.
On Tue, Aug 18, 2009 at 02:42, Ryan
Schmidt<su...@ryandesign.com> wrote:
>
> "The root of <url> is <shorter-url>."
>
> "The tree containing <url> is rooted at <shorter-url>."
>
Yea, actually --root is what I'd been using, though I neglected to put
it in my list. I'm not too keen on it because it's not specific
enough. The root of what? The project, the repository, the current
trunk-or-branch-or-tag (tobot?)
On Tue, Aug 18, 2009 at 12:22, Bolstridge,
Andrew<an...@intergraph.com> wrote:
>
> How about:
> Base (or Basis);
> Foundation;
> Source;
> Root (not keen on this one)
> Top;
> Terminus.
>
> I like Foundation best, "...go to the project foundation and click on
> tags to see..."
Of these, I think base or foundation has appeal. Top not so much for
the same reason as root. (Though it's appealingly short.)
On Tue, Aug 18, 2009 at 15:10, Ryan
Schmidt<su...@ryandesign.com> wrote:
> On Aug 18, 2009, at 07:41, Les Mikesell wrote:
[...snip...]
>> Why not just call it the project?
>
> He's not looking for a word for the project. He's looking for a word that
> can be used to describe the trunk, or any branch, or any tag, of the
> project.
correct. In fact, let me draw a picture. (please put on your ascii-art goggles)
svn://example.com/svn/repo/group/artifact/branches/ISSUE-13/src/main/java/com
\________________________/\_____________/\_______/\_______/\______________...
repository root url project name *mumble* *mumble* *mumble*-relative
"repo" kind name path
\_______________________________________/
project url
\________________________________________________________/
*mumble* url
Where in the case of trunk, this looks a little different:
.../group/artifact/trunk/src/main/java/com
\______/
*mumble*
kind &
name
..._____________________/
*mumble* url
On Tue, Aug 18, 2009 at 15:21, Luke Imhoff<lu...@cray.com> wrote:
>
> In my code and docs for the tools I build on top of Subversion I call that
> the version path.
"version path". Yea, we've been calling projects (see diagram)
"versionierbare Einheit" around the office (~ thing that can be
Versioned).
On Tue, Aug 18, 2009 at 15:29, Radomir
Zoltowski<ra...@s3group.com> wrote:
>
> In fact, all of these are just "copies". Am I right?
They are copies, but so are lots of other things. I though of "clones"
last night, but that misses this point that they can (and do) change.
Unless they are tags. Usually.
On Tue, Aug 18, 2009 at 15:35, Tony Sweeney<ts...@omnifone.com> wrote:
>
> I personally use 'variant' as a one-word placeholder for an instance of
> a trunk/tag/branch.
I like variant.
So far:
I've been using "stream", while I wait for your suggestions to come
in, though using that term is looking more like unfortunate
overloading [1]. Still, it doesn't appear to be used *within* the
Subversion community, so the collision is not so bad.
I like "variant" and "base"; even "copy". The perverse devil on my
left shoulder keeps trying to get me to use "furcate", but I don't
think that's going to fly.
[1] http://www.cmcrossroads.com/bradapp/acme/branching/
// Ben
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384786
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: looking for one word to encompass trunk, tag and branch
Posted by Tony Sweeney <ts...@omnifone.com>.
I personally use 'variant' as a one-word placeholder for an instance of
a trunk/tag/branch.
Tony.
> -----Original Message-----
> From: Ryan Schmidt [mailto:subversion-2009b@ryandesign.com]
> Sent: 18 August 2009 14:10
> To: Les Mikesell
> Cc: Bolstridge, Andrew; B. Smith-Mannschott;
> users@subversion.tigris.org
> Subject: Re: looking for one word to encompass trunk, tag and branch
>
> On Aug 18, 2009, at 07:41, Les Mikesell wrote:
>
> > Bolstridge, Andrew 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.
> >>
> >> How about:
> >> Base (or Basis);
> >> Foundation;
> >> Source;
> >> Root (not keen on this one)
> >> Top;
> >> Terminus.
> >>
> >> I like Foundation best, "...go to the project foundation
> and click on
> >> tags to see..."
> >
> > Why not just call it the project?
>
> He's not looking for a word for the project. He's looking for
> a word that can be used to describe the trunk, or any branch,
> or any tag, of the project.
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&
> dsMessageId=2384764
>
> To unsubscribe from this discussion, e-mail:
> [users-unsubscribe@subversion.tigris.org].
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit
> http://www.messagelabs.com/email
> ______________________________________________________________________
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384774
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by Jim Thompson <ji...@doit.wisc.edu>.
Ryan Schmidt wrote:
> On Aug 18, 2009, at 07:41, Les Mikesell wrote:
>
>
>> Bolstridge, Andrew 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.
>>>>
>>> How about:
>>> Base (or Basis);
>>> Foundation;
>>> Source;
>>> Root (not keen on this one)
>>> Top;
>>> Terminus.
>>>
>>> I like Foundation best, "...go to the project foundation and click on
>>> tags to see..."
>>>
>> Why not just call it the project?
>>
>
> He's not looking for a word for the project. He's looking for a word
> that can be used to describe the trunk, or any branch, or any tag, of
> the project.
>
>
I've been doing some scripting and here's the naming scheme used in my
stuff...
- root (e.g., https://..../regular)
- module
- middle (e.g., TTB, release, whatever)
- tail (e.g., test, qa, prod)
I glue those together (in the script) to get the full Url string. I've
got other stuff going on in the tail - a full tail might look like
test_20090818_1135_jft - and the script has a "find last" option.
The names (root, module, ...) were arbitrary - we're just talking about
pieces of a string and users may or may not conform to the TTB suggestion.
Cheers,
Jim
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384764
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384845
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by Radomir Zoltowski <ra...@s3group.com>.
Luke Imhoff wrote:
> Ryan Schmidt wrote:
>
>> On Aug 18, 2009, at 07:41, Les Mikesell wrote:
>>
>>
>>
>>> Bolstridge, Andrew 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.
>>>>>
>>>>>
>>>> How about:
>>>> Base (or Basis);
>>>> Foundation;
>>>> Source;
>>>> Root (not keen on this one)
>>>> Top;
>>>> Terminus.
>>>>
>>>> I like Foundation best, "...go to the project foundation and click on
>>>> tags to see..."
>>>>
>>>>
>>> Why not just call it the project?
>>>
>>>
>> He's not looking for a word for the project. He's looking for a word
>> that can be used to describe the trunk, or any branch, or any tag, of
>> the project.
>>
>> ------------------------------------------------------
>> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384764
>>
>> To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
>>
>>
> In my code and docs for the tools I build on top of Subversion I call
> that the version path.
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384768
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
>
Try thesaurus:
http://thesaurus.reference.com/browse/branch
In fact, all of these are just "copies". Am I right?
Radomir
The information contained in this e-mail and in any attachments is confidential and is designated solely for the attention of the intended recipient(s). If you are not an intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or any part thereof. If you have received this e-mail in error, please notify the sender by return e-mail and delete all copies of this e-mail from your computer system(s).
Please direct any additional queries to: communications@s3group.com.
Thank You.
Silicon and Software Systems Limited. Registered in Ireland no. 378073.
Registered Office: South County Business Park, Leopardstown, Dublin 18
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384772
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by Luke Imhoff <lu...@cray.com>.
Ryan Schmidt wrote:
> On Aug 18, 2009, at 07:41, Les Mikesell wrote:
>
>
>> Bolstridge, Andrew 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.
>>>>
>>> How about:
>>> Base (or Basis);
>>> Foundation;
>>> Source;
>>> Root (not keen on this one)
>>> Top;
>>> Terminus.
>>>
>>> I like Foundation best, "...go to the project foundation and click on
>>> tags to see..."
>>>
>> Why not just call it the project?
>>
>
> He's not looking for a word for the project. He's looking for a word
> that can be used to describe the trunk, or any branch, or any tag, of
> the project.
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384764
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
>
In my code and docs for the tools I build on top of Subversion I call
that the version path.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384768
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Aug 18, 2009, at 07:41, Les Mikesell wrote:
> Bolstridge, Andrew 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.
>>
>> How about:
>> Base (or Basis);
>> Foundation;
>> Source;
>> Root (not keen on this one)
>> Top;
>> Terminus.
>>
>> I like Foundation best, "...go to the project foundation and click on
>> tags to see..."
>
> Why not just call it the project?
He's not looking for a word for the project. He's looking for a word
that can be used to describe the trunk, or any branch, or any tag, of
the project.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384764
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by Les Mikesell <le...@gmail.com>.
Bolstridge, Andrew 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.
>>
>
> How about:
> Base (or Basis);
> Foundation;
> Source;
> Root (not keen on this one)
> Top;
> Terminus.
>
> I like Foundation best, "...go to the project foundation and click on
> tags to see..."
Why not just call it the project?
--
Les Mikesell
lesmikesell@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384750
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: looking for one word to encompass trunk, tag and branch
Posted by "Bolstridge, Andrew" <an...@intergraph.com>.
> -----Original Message-----
> From: B. Smith-Mannschott [mailto:bsmith.occs@gmail.com]
> Sent: Monday, August 17, 2009 8:52 PM
> To: users@subversion.tigris.org
> Subject: looking for one word to encompass trunk, tag and branch
>
> 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.
>
How about:
Base (or Basis);
Foundation;
Source;
Root (not keen on this one)
Top;
Terminus.
I like Foundation best, "...go to the project foundation and click on
tags to see..."
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384688
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by Les Mikesell <le...@gmail.com>.
B. Smith-Mannschott wrote:
>
>> It's not a one word name, but I've refer to is as "the revision part of the
>> URL" or the "URL revision specifier".
>
> That's interesting! You seem to be using "revision" in the same
> fashion as Les Mikesell -- a usage I don't follow at all. I'd be
> curious to know where it originated.
>
> Every commit in Subversion creates a new /Revision/ of the *entire*
> repository, which typically shares structure with previous revisions.
> (The Subversion book has a nice figure illustrating this.[1]) These
> revisions are ordered and numbered (thus the revision number).
It does, and this is useful in a transactional sense and to maintain
sanity when a newer chunk of the tree is moved under a long-unchanged
branch. But, the part you are interested in is always identified by a
path and a revision number.
> [1] http://svnbook.red-bean.com/en/1.5/svn.basic.in-action.html#svn.basic.in-action.revs.dia-1
>
> Given this definition, it makes sense to say that the subtree named by
> some URL has remained unchanged since revision N. (i.e. was last
> changed as part of the Nth commit.)
But it is normally irrelevant that some set of revisions n to
n+something are identical for a particular path. You either know some
number n or lower as a result of remembering/logging why you might want
it back, or you want the current HEAD and if or how much it has advanced
doesn't matter. Why does it matter to you that revisions
N+some_intermediate_value can be named but don't have changes under a
particular path?
> By the same definition, it would
> *never* have occurred to me to refer to the tail of a Subversion URL
> (or equivalently a subtree of the repository) as the "revision part".
You always need the path for the location in 'space' and the revision
number for the location in 'time'. The contents are what you put there.
> In any event, I'm afraid your solution wouldn't work for us because of
> this clash with our usage.
What other usage can you have for a path and revision number other than
to identify the revision of the thing you want? Since the revision
numbers are global, there can't be any conflicts - that is, a path and
revision number can only refer to one set of contents, which is whatever
was there at the end of the relevant commit. Maybe you'd be better off
thinking of what is called the revision number as a transaction number
since it doesn't mean that contents were revised in all locations, just
that some change happened somewhere in the repository. So what you
always get are the contents of a location at the time the specified
transaction completed.
--
Les Mikesell
lesmikesell@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2385390
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by "B. Smith-Mannschott" <bs...@gmail.com>.
On Wed, Aug 19, 2009 at 17:39, David Weintraub<qa...@gmail.com> wrote:
> It's not a one word name, but I've refer to is as "the revision part of the
> URL" or the "URL revision specifier".
That's interesting! You seem to be using "revision" in the same
fashion as Les Mikesell -- a usage I don't follow at all. I'd be
curious to know where it originated.
Every commit in Subversion creates a new /Revision/ of the *entire*
repository, which typically shares structure with previous revisions.
(The Subversion book has a nice figure illustrating this.[1]) These
revisions are ordered and numbered (thus the revision number).
[1] http://svnbook.red-bean.com/en/1.5/svn.basic.in-action.html#svn.basic.in-action.revs.dia-1
Given this definition, it makes sense to say that the subtree named by
some URL has remained unchanged since revision N. (i.e. was last
changed as part of the Nth commit.) By the same definition, it would
*never* have occurred to me to refer to the tail of a Subversion URL
(or equivalently a subtree of the repository) as the "revision part".
In any event, I'm afraid your solution wouldn't work for us because of
this clash with our usage.
// ben
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2385376
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by David Weintraub <qa...@gmail.com>.
It's not a one word name, but I've refer to is as "the revision part of the
URL" or the "URL revision specifier".
--
David Weintraub
qazwart@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2385273
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by Hari Kodungallur <hk...@gmail.com>.
On Mon, Aug 17, 2009 at 12:52 PM, B. Smith-Mannschott <bsmith.occs@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@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Aug 17, 2009, at 14:52, B. Smith-Mannschott wrote:
> 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*? [snip]
Not humorous but how about:
"The root of <url> is <shorter-url>."
"The tree containing <url> is rooted at <shorter-url>."
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384585
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: looking for one word to encompass trunk, tag and branch
Posted by "B. Smith-Mannschott" <bs...@gmail.com>.
On Wed, Aug 19, 2009 at 19:18, Oefelein,
Martina<Ma...@dionex.com> wrote:
>
> How about "codeline"?
>
That's a good suggestion. It brings much of the same meaning as
"stream", without already being overloaded by a more specific meaning.
(At least as far as I'm aware.)
(I'm not a great fan of overloading one word with multiple meanings.
At least not in technical writing. In verse, it's ok.)
> This is sometimes used to designate trunk and branches, with the trunk
> also called "main codeline".
> It's a bit of a stretch to extend it to a tag, which doesn't change. One
> could say it is a codeline shrunk down to a single point ("codepoint"?)
"codepoint". cute. Although it'd still consider it a codeline (it does
retain its history, after all). It's just static.
// ben
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2385382
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: looking for one word to encompass trunk, tag and branch
Posted by "Oefelein, Martina" <Ma...@dionex.com>.
Hi Ben,
How about "codeline"?
This is sometimes used to designate trunk and branches, with the trunk
also called "main codeline".
It's a bit of a stretch to extend it to a tag, which doesn't change. One
could say it is a codeline shrunk down to a single point ("codepoint"?)
Ciao
Martina
-----Original Message-----
From: B. Smith-Mannschott [mailto:bsmith.occs@gmail.com]
Sent: Monday, August 17, 2009 9:52 PM
To: users@subversion.tigris.org
Subject: looking for one word to encompass trunk, tag and branch
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.
thanks,
// Ben
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageI
d=2384505
To unsubscribe from this discussion, e-mail:
[users-unsubscribe@subversion.tigris.org].
Dionex Softron GmbH
Rechtsform: Gesellschaft mit beschrankter Haftung
Sitz der Gesellschaft: Germering
Geschaftsfuhrer: Dr. Peter Jochum
Zustandiges Registergericht: Amtsgericht Munchen, HRB 717 65
Dionex Softron GmbH
Rechtsform: Gesellschaft mit beschrankter Haftung
Sitz der Gesellschaft: Germering
Geschaftsfuhrer: Dr. Peter Jochum
Zustandiges Registergericht: Amtsgericht Munchen, HRB 717 65
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2385315
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: looking for one word to encompass trunk, tag and branch
Posted by Ul...@elektrobit.com.
B. Smith-Mannschott 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 not happy with any of these options and open to any suggestions.
> Clever, evocative and humorous ideas get bonus points.
What about "structure" or "project-structure"? That can be everything - documentation, source code, whatever.
Cheers,
Ulli
--
Ullrich Jans, Application Support, IM
Phone: +49 9131 7701-6627, mailto:ullrich.jans@elektrobit.com
Fax: +49 9131 7701-6333, www.elektrobit.com
Elektrobit Automotive GmbH, Am Wolfsmantel 46, 91058 Erlangen, Germany
Managing Directors: Otto Fößel, Jarkko Sairanen
Register Court Fürth HRB 4886
----------------------------------------------------------------
Please note: This e-mail may contain confidential information
intended solely for the addressee. If you have received this
e-mail in error, please do not disclose it to anyone, notify
the sender promptly, and delete the message from your system.
Thank you.
Re: looking for one word to encompass trunk, tag and branch
Posted by Michael Haggerty <mh...@alum.mit.edu>.
B. Smith-Mannschott wrote:
> 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:
I struggled with this same naming question when modifying and
documenting cvs2svn, and the best I could come up with was
LineOfDevelopment (often abbreviated to "lod"). But I was never very
happy with it (mostly because it is so long).
Michael
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2385011
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].