All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Add support for url aliases in config files
Date: Wed, 20 Feb 2008 11:42:00 -0800	[thread overview]
Message-ID: <7vskzn4dpz.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0802201418590.19024@iabervon.org> (Daniel Barkalow's message of "Wed, 20 Feb 2008 14:24:50 -0500 (EST)")

Daniel Barkalow <barkalow@iabervon.org> writes:

> On Wed, 20 Feb 2008, Junio C Hamano wrote:
> ...
>> To me, "url.$this_is_what_I_use.aka = $how_they_might_call_it"
>> initially felt backwards, but the point of the facility is to
>> allow mapping many ways other people might call it to how you
>> would (and the other way would not make sense as allowing to map
>> one thing to multiple is only to introduce unnecessary
>> ambiguity), so it makes perfect sense.
>
> This order of values is definitely the right thing, for the mapping 
> reasons you saw. And I think "aka" is generally used to indicate 
> additional non-canonical names for something with an official name (see, 
> for example, IMDB's usage). I haven't been able to come up with anything 
> better to indicate "this is a name that I will recognize but not use 
> myself".

Yeah, that "aka" is still disturbing.

	[url A]
        	aka = B

would read to me: "A is also known as B" but that is clearly not
what it means here.  You would want this:

	[url A]
        	aka = B 
		aka = C

to mean "B is also known as A.  C is also known as A."  IOW, you
are using it backwards, because their name is more official and
you are using your own unofficial name to call it.

Sorry, but I cannot think of a better way to resolve this, other
than by spelling the keyword backwards, but that still makes it
"aka".

>> > diff --git a/Documentation/urls.txt b/Documentation/urls.txt
>> > index 81ac17f..0115af7 100644
>> > --- a/Documentation/urls.txt
>> > +++ b/Documentation/urls.txt
>> > @@ -44,3 +44,26 @@ endif::git-clone[]
>> > ...
>> > +If you have a section:
>> > +
>> > +------------
>> > +	[host "git://git.host.xz/"]
>> > +		aka = host.xz:/path/to/
>> > +		aka = work:
>> > +------------
>> > +
>> > +a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
>> > +rewritten in any context that takes a URL to be
>> > +"git://git.host.xz/repo.git".
>> 
>> This still stands???
>
> And missed the "host"->"url" bit while I fixed the rest of the example. 

So this part is not wanted, right?

> Want a replacement, or can you make the obvious corrections just as 
> easily yourself?

If my above rant about "aka" is not a total misunderstanding,
I'd rather see somebody (could be you, or others on the list) to
come up with a better keyword and have a replacement patch based
on it.

  reply	other threads:[~2008-02-20 19:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 18:43 [PATCH 2/2] Add support for url aliases in config files Daniel Barkalow
2008-02-20 19:15 ` Junio C Hamano
2008-02-20 19:24   ` Daniel Barkalow
2008-02-20 19:42     ` Junio C Hamano [this message]
2008-02-20 19:54       ` Jay Soffian
2008-02-20 20:42       ` Daniel Barkalow
2008-02-20 22:02       ` しらいしななこ
2008-02-20 22:22         ` Johannes Schindelin
2008-02-21  0:47           ` Junio C Hamano
2008-02-21  1:26             ` Jay Soffian
2008-02-21  1:47               ` Linus Torvalds
2008-02-21  2:19                 ` Jay Soffian
2008-02-21  5:04                 ` Daniel Barkalow
2008-02-21  5:34                   ` Junio C Hamano
2008-02-25  4:08                     ` Junio C Hamano
2008-02-25  4:30                       ` Daniel Barkalow
2008-02-25  6:22                         ` Junio C Hamano
2008-02-25  6:35                           ` Daniel Barkalow
2008-02-21 16:31                 ` Jon Loeliger
2008-02-20 19:49     ` Jay Soffian
2008-02-20 19:58       ` Junio C Hamano
2008-02-20 20:22         ` Jay Soffian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vskzn4dpz.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.