git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Kramer <benny.kra@googlemail.com>
To: Andreas Ericsson <ae@op5.se>
Cc: Benjamin Kramer <benny.kra@googlemail.com>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
	jdl@jdl.com
Subject: Re: [PATCH/RFC] daemon.c: replace inet_ntop with getnameinfo
Date: Thu, 7 May 2009 14:54:43 +0200	[thread overview]
Message-ID: <EC96A79E-4D4E-467A-A10F-D905FE02E508@gmail.com> (raw)
In-Reply-To: <4A02D70B.6090305@op5.se>


Andreas Ericsson wrote:

> What per-IP directories are you talking about?

git daemon has a feature called interpolated paths

If git daemon is started like this:
     git daemon --interpolated-path=%IP/%D
(the machine has two IPs: 123.123.123.123 (v4) and 2001:db8::1 (v6))
and someone clones a repository:
     git clone git://123.123.123.123/frotz
git daemon will look for the repository in the directory  
`123.123.123.123/frotz'

But if git daemon listens on the IPv6 interface and someone clones a  
repository:
     git clone git://2001:db8::1/frotz
Then git daemon will look for the repository in `0.0.0.0/frotz'

My patch makes it converting IPv6 addresses properly and if you the  
clone
in my previous example it'll now look in `2001:db8::1/frotz' (with  
colons in the
directory name)

I hope my intentions are now a bit clearer ;)

  reply	other threads:[~2009-05-07 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 12:22 [PATCH/RFC] daemon.c: replace inet_ntop with getnameinfo Benjamin Kramer
2009-05-07 12:41 ` Andreas Ericsson
2009-05-07 12:54   ` Benjamin Kramer [this message]
2009-05-07 13:15     ` Johannes Sixt
2009-05-07 14:30       ` Benjamin Kramer
2009-05-07 13:34     ` Jakub Narebski
2009-05-07 13:45       ` Brian Gernhardt
2009-05-07 13:51       ` Miles Bader

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=EC96A79E-4D4E-467A-A10F-D905FE02E508@gmail.com \
    --to=benny.kra@googlemail.com \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jdl@jdl.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).