From: "Brian J. Murrell" <brian-SquOHqY54CVWr29BmMi2cA@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: Re: ipv6 status
Date: Mon, 01 Dec 2008 13:40:02 -0500 [thread overview]
Message-ID: <1228156802.6497.277.camel@pc.interlinx.bc.ca> (raw)
In-Reply-To: <D9F679A4-0664-4977-9DAF-5EC0AF2BADD8@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 235 bytes --]
On Mon, 2008-12-01 at 13:33 -0500, Chuck Lever wrote:
>
> There isn't a published roadmap. Linux developers tend to eschew
> deadlines.
Indeed. :-)
Thanx for the update. Looking forward to it finally finishing.
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-12-01 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 0:40 ipv6 status Brian J. Murrell
[not found] ` <1228092016.7394.521.camel-lA68w17JHpfIgqYUaR6mlLDks+cytr/Z@public.gmane.org>
2008-12-01 18:33 ` Chuck Lever
2008-12-01 18:40 ` Brian J. Murrell [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=1228156802.6497.277.camel@pc.interlinx.bc.ca \
--to=brian-squohqy54cvwr29bmmi2ca@public.gmane.org \
--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