From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Jon Loeliger <jdl@freescale.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 2/2] Add support for host aliases in config files
Date: Tue, 19 Feb 2008 13:35:32 -0800 [thread overview]
Message-ID: <7vy79ghbob.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: alpine.LNX.1.00.0802191127080.19024@iabervon.org
Daniel Barkalow <barkalow@iabervon.org> writes:
> On Tue, 19 Feb 2008, Jon Loeliger wrote:
>
>> Also, is "host" really the right config key? Maybe "rewritehost"?
>> Or is this thought to be the basis of other (perhaps not rewrite
>> related) properties of the same host as well?
>
> I think it's likely that other properties of the host could show up. I
> suspect that uploadpack and receivepack would be useful host-wide if you
> were using a lot of ad-hoc repository names on a big site. Rewriting the
> URLs is just the itch I had with this scope.
I'd agree that per-host configuration may be useful, and your
"paths to programs" may be a good example. But I think it is
plausible that a host needs multiple <rewritefrom,rewriteto>
tuples. Either your '[host "$this_url"] aka = $that_url' or
Dscho's earlier '[rewrite "$this_url_to"] url = $that_url' shows
that this is not about host but "prefix part of URL".
next prev parent reply other threads:[~2008-02-19 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 4:28 [PATCH 2/2] Add support for host aliases in config files Daniel Barkalow
2008-02-19 15:11 ` Jon Loeliger
2008-02-19 15:49 ` Johannes Schindelin
2008-02-19 16:52 ` Daniel Barkalow
2008-02-20 19:44 ` Jakub Narebski
2008-02-19 16:45 ` Daniel Barkalow
2008-02-19 21:35 ` Junio C Hamano [this message]
2008-02-20 0:02 ` Daniel Barkalow
2008-02-20 1:01 ` Johannes Schindelin
2008-02-20 1:04 ` Junio C Hamano
2008-02-20 1:14 ` Johannes Schindelin
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=7vy79ghbob.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=jdl@freescale.com \
--cc=jnareb@gmail.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).