From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Daniel Barkalow" <barkalow@iabervon.org>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] Add support for url aliases in config files
Date: Wed, 20 Feb 2008 14:49:06 -0500 [thread overview]
Message-ID: <76718490802201149w5a7c0b88udef968f4083190ea@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0802201418590.19024@iabervon.org>
On Feb 20, 2008 2:24 PM, Daniel Barkalow <barkalow@iabervon.org> wrote:
> 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".
I think the word you want is "alias", isn't it? I've never really seen
aka used in a technical sense, whereas alias is used quite often (URL
aliases, DNS aliases, etc). So:
url.$canonical_name.alias = $local_name.
$0.02.
j.
next prev parent reply other threads:[~2008-02-20 19:49 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
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 [this message]
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=76718490802201149w5a7c0b88udef968f4083190ea@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).