From: Adrian Bunk <bunk@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: harvey.harrison@gmail.com, torvalds@linux-foundation.org,
davem@davemloft.net, tglx@linutronix.de, hpa@zytor.com,
xemul@openvz.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] feature-removal: add documentation for exported symbols going away
Date: Thu, 14 Feb 2008 01:22:48 +0200 [thread overview]
Message-ID: <20080213232248.GF12383@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080213145405.35fb5733.akpm@linux-foundation.org>
On Wed, Feb 13, 2008 at 02:54:05PM -0800, Andrew Morton wrote:
> On Thu, 14 Feb 2008 00:43:08 +0200
> Adrian Bunk <bunk@kernel.org> wrote:
>
> > There's simply no point in treating the removal of exports differently
> > from the many other API breaks we have in each release.
>
> I have repeatedly and relatively patiently explained to you what the
> point is. Simply saying that there isn't one doesn't actually make
> it go away.
Yes, we had this when you insisted on the deprecation period for
sys_open which still brings me to explosion each time such topics come
up and brought you _very_ near at being the first person ever in my
killfile.
I don't get your point why bigger API changes should still be allowed
without any advance warning while removing an export should require
deprecation periods.
If you want to offer a stable API for external modules then please do
it completely and with all consequences.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-02-13 23:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 22:22 Harvey Harrison
2008-02-13 22:34 ` Adrian Bunk
2008-02-13 22:42 ` Harvey Harrison
2008-02-13 22:55 ` Adrian Bunk
2008-02-13 22:43 ` Adrian Bunk
2008-02-13 22:54 ` Andrew Morton
2008-02-13 23:22 ` Adrian Bunk [this message]
2008-02-13 23:43 ` Andrew Morton
2008-02-13 23:58 ` Adrian Bunk
2008-02-14 0:18 ` Alan Cox
2008-02-13 23:07 ` Arjan van de Ven
2008-02-15 3:06 ` Rene Herman
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=20080213232248.GF12383@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=xemul@openvz.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 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®