From: Fabien Ribes <fribes@capgemini.fr>
To: "David S. Miller" <davem@redhat.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Networking: RFC1122 and 1123 status for kernel 2.4
Date: Fri, 08 Dec 2000 17:19:30 +0100 [thread overview]
Message-ID: <3A310A12.446E2C4A@capgemini.fr> (raw)
In-Reply-To: <3A30F463.2EE04F4E@capgemini.fr> <200012081454.GAA02632@pizda.ninka.net> <20001208163154.A20038@gruyere.muc.suse.de>
Andi Kleen a écrit :
>
> On Fri, Dec 08, 2000 at 06:54:28AM -0800, David S. Miller wrote:
> > Date: Fri, 08 Dec 2000 15:46:59 +0100
> > From: Fabien Ribes <fribes@capgemini.fr>
> >
> > Looking at Linux kernel sources, I've found RFC1122 status splitted in
> > each file. Is there a complete document showing RFC1122 status as a
> > whole for a given kernel version ?
> >
> > No, unfortunately nobody has the time to do this.
>
> The RFC evaluation is also out of date and should be either redone or removed.
Indeed, what I need is some kind of paper insurance of interoperability
... so I believe grepping the sources for compliances will do the trick.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-08 16:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 14:46 Networking: RFC1122 and 1123 status for kernel 2.4 Fabien Ribes
2000-12-08 14:54 ` David S. Miller
2000-12-08 15:31 ` Andi Kleen
2000-12-08 15:28 ` David S. Miller
2000-12-08 15:58 ` Andi Kleen
2000-12-08 16:41 ` kuznet
2000-12-08 16:48 ` Andi Kleen
2000-12-08 17:14 ` Alan Cox
2000-12-08 17:13 ` Alan Cox
2000-12-08 19:06 ` kuznet
2000-12-08 19:34 ` Christoph Hellwig
2000-12-08 23:17 ` Christoph Hellwig
2000-12-09 0:00 ` Alan Cox
2000-12-11 22:06 ` David S. Miller
2000-12-13 17:14 ` Fabien Ribes
2000-12-13 17:01 ` David S. Miller
2000-12-08 16:19 ` Fabien Ribes [this message]
2000-12-08 16:37 ` Andi Kleen
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=3A310A12.446E2C4A@capgemini.fr \
--to=fribes@capgemini.fr \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.