Thanks for all the great replies.
On Tue, Aug 18, 2009 at 00:14, Hari Kodungallur<hkodungallur_at_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<subversion-2009b_at_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<andy.bolstridge_at_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<subversion-2009b_at_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<luke_at_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<radomir.zoltowski_at_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<tsweeney_at_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_at_subversion.tigris.org].
Received on 2009-08-18 16:27:04 CEST