netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Seong Moon" <seong@etri.re.kr>
To: <netdev@oss.sgi.com>
Subject: IPv6 development plan ?
Date: Fri, 8 Nov 2002 18:10:23 +0900	[thread overview]
Message-ID: <010101c28706$b1767840$21abfe81@seong> (raw)

Hi theres!

I know that the kernel.org and the usagi have developed the IPv6
functionality seperately.
The usagi says that the their product has applied the kernel.org partially.
Why does not the original kernel apply the entire usagi patch ?

And I want to know the master plan of development of IPv6 including IPv6
routing functions.
Could I know the schedule or plan ?

I read the Linux IPv6 HOWTO written by Peter Bieringer.
He said that 2.6.x kernel series will contain a true and up-to-date IPv6
implementation.
Approximately When can I use 2.6.x kernel ?

TIA

             reply	other threads:[~2002-11-08  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-08  9:10 Seong Moon [this message]
2002-11-08  9:22 ` IPv6 development plan ? bert hubert

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='010101c28706$b1767840$21abfe81@seong' \
    --to=seong@etri.re.kr \
    --cc=netdev@oss.sgi.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).