From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chucklever@gmail.com>
Cc: Libtirpc-devel Mailing List
<libtirpc-devel@lists.sourceforge.net>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [Libtirpc-devel] [PATCH v2] Make IPv6 enabled by default
Date: Wed, 28 May 2014 12:20:00 -0400 [thread overview]
Message-ID: <53860CB0.9040106@RedHat.com> (raw)
In-Reply-To: <3B5A58F2-25AB-4F5E-8901-A9CFADBA959D@gmail.com>
On 05/27/2014 02:37 PM, Chuck Lever wrote:
>
>
>> On May 27, 2014, at 2:18 PM, Steve Dickson <steved@redhat.com> wrote:
>>
>> From: Mike Frysinger <vapier@gentoo.org>
>>
>> Added a --disable-ipv6 configuration flag to allow the
>> disabling of the IPv6 support.
>
> If I may ask, who needs to disable it?
Nobody... I just sent out the wrong patch....
Sorry for the noise...
steved.
prev parent reply other threads:[~2014-05-28 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 18:18 [PATCH v2] Make IPv6 enabled by default Steve Dickson
2014-05-27 18:37 ` [Libtirpc-devel] " Chuck Lever
2014-05-28 16:20 ` Steve Dickson [this message]
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=53860CB0.9040106@RedHat.com \
--to=steved@redhat.com \
--cc=chucklever@gmail.com \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@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).