From: Quantum Scientific <Info@Quantum-Sci.com>
To: netdev@oss.sgi.com
Subject: Re: Kernel 2.6 IPV6 Busted
Date: Sun, 27 Feb 2005 12:08:52 -0600 [thread overview]
Message-ID: <200502271208.52936.Info@Quantum-Sci.com> (raw)
In-Reply-To: <20050228.022828.120983354.yoshfuji@linux-ipv6.org>
On Sunday 27 February 2005 11:28, YOSHIFUJI Hideaki / 吉藤英明 wrote:
> Don't you find diff files?! e.g:
>
ftp://ftp.linux-ipv6.org/pub/usagi/snap/split/usagi-linux26-s20050214-2.6.11-rc3.diff.bz2
> is patch against linux-2.6.11-rc3.
I see. I was talking about the downloadable split and kit archives, and you
were talking about what's on FTP, which I didn't expect to be different.
I'm hoping some of my vociferous effort to make this go, will help improve
things down the line. IPV6 is extremely difficult to implement at the
moment.
Here's hoping the USAGI linux-2.6.10-rc3 diff fits in Debian
kernel-source-2.6.10-5. Back to work...
Carl Cook
next prev parent reply other threads:[~2005-02-27 18:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 15:28 Kernel 2.6 IPV6 Busted Quantum Scientific
2005-02-27 16:10 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-27 16:29 ` Quantum Scientific
2005-02-27 17:28 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-27 18:08 ` Quantum Scientific [this message]
2005-03-15 5:00 ` Horms
2005-02-27 17:40 ` Andre Tomt
2005-02-27 18:20 ` Quantum Scientific
2005-02-27 18:59 ` Jeff Garzik
2005-02-27 19:10 ` Quantum Scientific
2005-02-27 19:58 ` Jeff Garzik
2005-02-27 20:10 ` Quantum Scientific
2005-02-27 21:35 ` David S. Miller
2005-03-01 10:07 ` Denis Vlasenko
2005-03-01 13:50 ` Quantum Scientific
2005-03-01 16:26 ` Jeff Garzik
2005-03-01 20:46 ` Tomasz Torcz
2005-03-01 23:55 ` Quantum Scientific
2005-03-02 14:02 ` Denis Vlasenko
2005-03-02 19:12 ` Jeff Garzik
2005-03-01 21:50 ` Andre Tomt
2005-03-01 23:59 ` Quantum Scientific
2005-02-27 18:12 ` Jeff Garzik
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=200502271208.52936.Info@Quantum-Sci.com \
--to=info@quantum-sci.com \
--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).