From: Junio C Hamano <gitster@pobox.com>
To: kusmabite@gmail.com
Cc: Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org, Jeff King <peff@peff.net>,
Eric Wong <normalperson@yhbt.net>
Subject: Re: [PATCH 0/5] transport: unify ipv4 and ipv6 code paths
Date: Mon, 11 Jun 2012 11:59:19 -0700 [thread overview]
Message-ID: <7v62ax7jzs.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CABPQNSb9EGOgHb7NtsEtDh2QkjkHYn7YemYsa8Yaqyuce-aDMw@mail.gmail.com> (Erik Faye-Lund's message of "Mon, 11 Jun 2012 20:12:00 +0200")
Erik Faye-Lund <kusmabite@gmail.com> writes:
> On Thu, Mar 8, 2012 at 1:48 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> Hi,
>>
>> These patches eliminate some ifdef-ery concerning NO_IPV6. I used
>> them when writing the SRV patch, which applies on top, but it's
>> probably best to think of it as an independent topic.
>>
>> Patch 4 is the heart of the series. It provides an interface similar
>> to getaddrinfo that can be implemented on top of either gethostbyname
>> or getaddrinfo and puts each implementation in a separate file. This
>> way, callers can just use the common API and they do not need to have
>> two copies of their code, one for each host resolution API.
>>
>> Patches 1-3 move code around until all the code that patch 4 touches
>> is in one place.
>>
>> Patches 5 is a potential error handling improvement noticed while
>> writing patches 1-4. It's probably not actually needed but it was a
>> comfort to me.
>>
>> These patches have been in use in Debian since June of last year. I'd
>> like to see this in mainline early in the 1.7.11 cycle to make coding
>> that touches this area during that cycle more pleasant. Thoughts of
>> all kinds welcome.
>
> What happened to this series?
Yeah, what happened to it? I was looking at the diff files Ubuntu
applies when generating its recent .deb files, and noticed these
patches today, and was wondering what was going on.
next prev parent reply other threads:[~2012-06-11 18:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 12:48 [PATCH 0/5] transport: unify ipv4 and ipv6 code paths Jonathan Nieder
2012-03-08 13:03 ` [PATCH 1/5] transport: expose git_tcp_connect() and friends in new tcp.h Jonathan Nieder
2012-03-08 15:28 ` Erik Faye-Lund
2012-03-08 13:05 ` [PATCH 2/5] daemon: make host resolution a separate function Jonathan Nieder
2012-03-08 13:06 ` [PATCH 3/5] daemon: move locate_host() to tcp lib Jonathan Nieder
2012-03-08 13:09 ` [PATCH 4/5] tcp: unify ipv4 and ipv6 code paths Jonathan Nieder
2012-03-08 15:39 ` Erik Faye-Lund
2012-03-08 21:10 ` Jonathan Nieder
2012-03-08 13:11 ` [PATCH 5/5] daemon: check for errors retrieving IP address Jonathan Nieder
2012-03-08 13:16 ` [PATCH 6/5] tcp: make dns_resolve() return an error code Jonathan Nieder
2012-03-08 13:21 ` [PATCH 7/5] transport: optionally honor DNS SRV records Jonathan Nieder
2012-03-08 16:18 ` Erik Faye-Lund
2012-03-08 21:35 ` Jonathan Nieder
2012-03-09 7:07 ` Johannes Sixt
2012-03-09 8:00 ` Jonathan Nieder
2012-03-08 13:23 ` [PATCH 8/5] srv: tolerate broken DNS replies Jonathan Nieder
2012-03-08 22:28 ` Richard Hartmann
2012-06-11 18:12 ` [PATCH 0/5] transport: unify ipv4 and ipv6 code paths Erik Faye-Lund
2012-06-11 18:59 ` Junio C Hamano [this message]
2012-06-14 5:02 ` Jonathan Nieder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v62ax7jzs.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=kusmabite@gmail.com \
--cc=normalperson@yhbt.net \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).