From: "David S. Miller" <davem@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: YOSHIFUJI Hideaki "/ ?$B5HF#1QL@?(B" <yoshfuji@linux-ipv6.org>,
Robert.L.Harris@rdlg.net, linux-kernel@vger.kernel.org
Subject: Re: IPv6 in the vanilla tree?
Date: 13 Feb 2003 12:00:09 -0800 [thread overview]
Message-ID: <1045166409.7435.6.camel@rth.ninka.net> (raw)
In-Reply-To: <20030213161100.A3399@infradead.org>
On Thu, 2003-02-13 at 08:11, Christoph Hellwig wrote:
> Btw, is there any chance you could make snapshot patches for 2.5 available
> as you do for 2.4? Given the number of change in the 2.4 tree it might be
> interesting what's still missing for 2.5.
ipv6 should be basically identical between 2.4.x and 2.5.x
The only difference is IPSEC, and even for that the ipv6
portions are still only in their most basic stages.
I bet that all their 2.4.x patches apply pretty cleanly to 2.5.x
prev parent reply other threads:[~2003-02-13 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 13:57 Robert L. Harris
2003-02-13 14:04 ` YOSHIFUJI Hideaki / 吉藤英明
2003-02-13 16:11 ` Christoph Hellwig
2003-02-13 20:00 ` David S. Miller [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=1045166409.7435.6.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=Robert.L.Harris@rdlg.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®