From: Arjan van de Ven <arjanv@redhat.com>
To: Sensei <senseiwa@tin.it>
Cc: David Lang <david.lang@digitalinsight.com>,
Krzysztof Halasa <khc@pm.waw.pl>, Adrian Bunk <bunk@stusta.de>,
linux-kernel@vger.kernel.org
Subject: Re: [INFO] Kernel strict versioning
Date: Thu, 14 Apr 2005 21:55:13 +0200 [thread overview]
Message-ID: <1113508514.6293.82.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <425EC778.4070009@tin.it>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
> I'd like API stability, if API stability is
> achieved, ABI is there.
this is a joke right? If you really think this you have no idea what ABI
stability means and how extremely hard it is to even sort of remotely
approach it.
Trust me. It's *extremely* hard to impossible. Several security fixes
can only be fixed this way. And it's REALLY fragile even if for other
fixes. And I am very glad that the linux kernel people in general decide
to not go for abi stability, the hacks that would be needed would be so
obscene and the gains very very minimal. (it's open source, you have the
source after all!)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-14 19:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 18:08 Franco "Sensei"
2005-04-08 19:05 ` Adrian Bunk
2005-04-12 1:02 ` Franco "Sensei"
2005-04-12 1:50 ` Adrian Bunk
2005-04-12 2:54 ` Franco "Sensei"
2005-04-12 11:28 ` Krzysztof Halasa
2005-04-12 17:22 ` Franco "Sensei"
2005-04-12 18:03 ` David Lang
2005-04-14 16:52 ` Franco "Sensei"
2005-04-14 17:57 ` David Lang
2005-04-14 19:41 ` Franco "Sensei"
2005-04-14 19:55 ` Arjan van de Ven [this message]
2005-04-14 22:33 ` Franco "Sensei"
2005-04-14 23:29 ` Al Viro
[not found] ` <425F33C2.8020301@tin.it>
2005-04-15 5:02 ` Al Viro
2005-04-14 20:01 ` Adrian Bunk
2005-04-14 22:51 ` Franco "Sensei"
2005-04-14 20:34 ` Horst von Brand
2005-04-14 22:45 ` Franco "Sensei"
2005-04-12 22:04 ` Krzysztof Halasa
2005-04-14 17:04 ` Franco "Sensei"
2005-04-12 22:43 ` Adrian Bunk
2005-04-14 17:40 ` Franco "Sensei"
2005-04-14 20:15 ` Adrian Bunk
2005-04-14 22:26 ` Franco "Sensei"
[not found] <3R6fp-7Qs-15@gated-at.bofh.it>
[not found] ` <3R71T-4S-15@gated-at.bofh.it>
[not found] ` <3Si4Q-Nh-21@gated-at.bofh.it>
[not found] ` <3SiRe-1eq-9@gated-at.bofh.it>
[not found] ` <3SjNh-1Yq-3@gated-at.bofh.it>
[not found] ` <3Ss48-qG-1@gated-at.bofh.it>
[not found] ` <3SxGA-5mR-29@gated-at.bofh.it>
2005-04-12 21:52 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
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=1113508514.6293.82.camel@laptopd505.fenrus.org \
--to=arjanv@redhat.com \
--cc=bunk@stusta.de \
--cc=david.lang@digitalinsight.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=senseiwa@tin.it \
/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®