From: Jon Loeliger <jdl@jdl.com>
To: git@vger.kernel.org
Subject: Re: git daemon directory munging?
Date: Sun, 04 Jun 2006 21:10:07 -0500 [thread overview]
Message-ID: <E1Fn4Xf-0000bL-82@jdl.com> (raw)
In-Reply-To: 44836803.5070405@zytor.com
> Well, you can bind different git daemons to different IP addresses
> (IP-based vhosting) or different ports (with SRV records in DNS.)
Is there existing support for telling the git-daemon what
specific IP to bind to out of an inetd setup and I just
missed it?
I could set that up realatively easily and gain the
functionality I wanted that way too.
I've also hacked in a host interpolation too.
But like you said, canonicalizing it and checking it is likely
a bit of a pain. I've side-stepped one angle of that by
symlinking in my /pub directory for multiple different
hostnames too. :-)
jdl
next reply other threads:[~2006-06-05 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 2:10 Jon Loeliger [this message]
2006-06-05 2:59 ` git daemon directory munging? H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2006-06-04 0:13 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
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=E1Fn4Xf-0000bL-82@jdl.com \
--to=jdl@jdl.com \
--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 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).