git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Jon Loeliger <jdl@freescale.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-daemon virtual hosting implementation.
Date: Thu, 24 Aug 2006 13:35:41 -0700	[thread overview]
Message-ID: <7vejv598iq.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1156450516.10054.276.camel@cashmere.sps.mot.com> (Jon Loeliger's message of "Thu, 24 Aug 2006 15:15:16 -0500")

Jon Loeliger <jdl@freescale.com> writes:

> On Wed, 2006-08-23 at 15:56, Pierre Habouzit wrote:
>
>> Another option would be not to support virtual hosts, but instead 
>> superseed the --base-path and --user-path with some --base-path-fmt 
>> and --user-path-fmt where the user can specify how to build the path 
>> with simple sprintf-like formats. One could e.g. support:
>>  * %% obviously ;
>>  * %h that will be replaced with the hostname
>>  * %u (only for --user-path-fmt)
>>  * %p (asked path)
>>  * ...
>
> And this is exactly what I have implemented and
> running on my system today!

Where is the patch ;-)?

  reply	other threads:[~2006-08-24 20:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23 18:52 [PATCH] git-daemon virtual hosting implementation Pierre Habouzit
2006-08-23 20:11 ` Junio C Hamano
2006-08-23 20:56   ` Pierre Habouzit
2006-08-24 20:15     ` Jon Loeliger
2006-08-24 20:35       ` Junio C Hamano [this message]
2006-08-24 20:34         ` Jon Loeliger
2006-08-23 23:32   ` [PATCH] git-daemon: more powerful base-path/user-path settings, using formats Pierre Habouzit
2006-08-24  0:17     ` Junio C Hamano
2006-08-24  7:50       ` Pierre Habouzit
2006-08-27  6:12     ` Junio C Hamano
2006-08-27 10:28       ` Pierre Habouzit
2006-08-27 10:52         ` Junio C Hamano
2006-08-27 11:40           ` Pierre Habouzit
2006-08-27 15:30             ` Jakub Narebski
2006-08-27 16:26               ` Pierre Habouzit
2006-08-27 16:06           ` Randal L. Schwartz

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=7vejv598iq.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=jdl@freescale.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).