From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Jon Loeliger <jdl@jdl.com>, git@vger.kernel.org
Subject: Re: git daemon directory munging?
Date: Sun, 04 Jun 2006 16:08:51 -0700 [thread overview]
Message-ID: <44836803.5070405@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606031722340.5498@g5.osdl.org>
Linus Torvalds wrote:
>
> On Sat, 3 Jun 2006, Jon Loeliger wrote:
>> <jdl> Thus, I'd use something like:
>> --map-base=www.foo.com/pub/scm:/pub/foo/scm
>> --map-base=www.bar.com/pub/scm=/pub/bar/scm
>
> The bigger problem is that nothing actually passes in the hostname to
> git-daemon in the first place. By the time the git-daemon is contacted,
> the hostname is long gone ;(
Well, you can bind different git daemons to different IP addresses
(IP-based vhosting) or different ports (with SRV records in DNS.)
> Now, you can just extend the git protocol to just pass in the host too.
>
> You can in fact do this in a backwards-compatible manner (old git-daemons
> will just ignore it, and new git daemons will automatically notice new
> clients) with something evil like the appended.
>
That's actually what was done to HTTP.
> Not tested (and this actualyl doesn't make the daemon _use_ the data, it
> just adds a comment - the rest "is left as an exercise for the reader")
-hpa
next prev parent reply other threads:[~2006-06-04 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 0:13 git daemon directory munging? Jon Loeliger
2006-06-04 0:42 ` Linus Torvalds
2006-06-04 6:27 ` Junio C Hamano
2006-06-04 23:10 ` H. Peter Anvin
2006-06-04 23:08 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-05 2:10 Jon Loeliger
2006-06-05 2:59 ` H. Peter Anvin
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=44836803.5070405@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=jdl@jdl.com \
--cc=torvalds@osdl.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.