From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Andi Kleen <ak@suse.de>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>,
Petr Vandrovec <VANDROVE@vc.cvut.cz>,
linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: Source code compatibility in Stable series????
Date: Fri, 11 May 2001 12:52:19 +0200 (MEST) [thread overview]
Message-ID: <200105111052.MAA18606@cave.bitwizard.nl> (raw)
In-Reply-To: <20010511124431.A6267@gruyere.muc.suse.de> from Andi Kleen at "May 11, 2001 12:44:31 pm"
Andi Kleen wrote:
> On Fri, May 11, 2001 at 12:39:29PM +0200, Rogier Wolff wrote:
> > But it's always been said that source code compatiblity would be
> > maintained. I'm a bit pissed that people just go about changing public
> > source-level interfaces.
>
> 2.4.4 is basically like 2.5.0 as far as networking is concerned, it includes major
> fundamental changes to the stack.
yeah. I noticed. I'm supposed to be happy about this?
I'll manage, and I'll "deal with it", but not before I've told you
that I'm not happy about it.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
next prev parent reply other threads:[~2001-05-11 10:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 12:21 Source code compatibility in Stable series???? Petr Vandrovec
2001-05-11 10:32 ` Andi Kleen
2001-05-11 10:39 ` Rogier Wolff
2001-05-11 10:44 ` Andi Kleen
2001-05-11 10:52 ` Rogier Wolff [this message]
2001-05-11 11:19 ` David S. Miller
2001-05-11 11:19 ` David S. Miller
2001-05-11 11:16 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2001-05-11 13:08 Petr Vandrovec
2001-05-11 9:47 Rogier Wolff
2001-05-11 9:56 ` David S. Miller
2001-05-11 10:03 ` Andi Kleen
2001-05-11 11:13 ` David S. Miller
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=200105111052.MAA18606@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=VANDROVE@vc.cvut.cz \
--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.