From: Greg KH <greg@kroah.com>
To: Daniel Hazelton <dhazelton@enter.net>
Cc: Heikki Orsila <shdl@zakalwe.fi>,
linux-kernel@vger.kernel.org, mpm@selenic.com, ak@suse.de,
m-ikeda@ds.jp.nec.com, zhongyu@18mail.cn, minchan.kim@gmail.com
Subject: Re: [PATCH] Improve Documentation/stable_api_nonsense.txt v2
Date: Sat, 2 Feb 2008 21:03:10 -0800 [thread overview]
Message-ID: <20080203050310.GA23824@kroah.com> (raw)
In-Reply-To: <200802021952.37848.dhazelton@enter.net>
On Sat, Feb 02, 2008 at 07:52:37PM -0500, Daniel Hazelton wrote:
> On Saturday 02 February 2008 19:22:49 Greg KH wrote:
> > On Sat, Feb 02, 2008 at 04:44:57PM +0200, Heikki Orsila wrote:
> <snip>
> > > @@ -145,6 +145,10 @@ as small as possible, and that all potential
> > > interfaces are tested as well as they can be (unused interfaces are
> > > pretty much impossible to test for validity.)
> > >
> > > +However, changing an interface can be delicate work and it can take
> > > +significant amount of developer effort. Therefore, an interface is
> > > +not changed unless the change is regarded as very important by the
> > > +developers.
> > >
> > > What to do
> > > ----------
> >
> > I still don't understand why you want to add these sentances. Why are
> > they needed? Are people thinking that the kernel developers just
> > randomly change things just because they are bored and have nothing else
> > to do at the moment? Do people think that our changes are gratuitous?
> >
> > Even so, I don't think this needs to be added, we have already stated
> > many good reasons why changing apis are necessary and good. Do need to
> > add another one?
> >
>
> Actually, Greg, a hell of a lot of people that don't track linux kernel
> development do think that way. And there are always going to be people that
> think that way.
So why would to more sentances trying to say "see, we really do know
what we are doing, we aren't idiots" make things any better to these
people? (hint, it wouldn't...)
> As it stands the recommended paragraph does clarify that, while the interfaces
> aren't stable, can and will change as needed, there are some core interfaces
> that *WON'T* change without a very good reason.
Again, do you think we kernel developers just randomly change core apis
because we are bored and want something to do late at night when we
can't sleep and are tired of playing Rock Band?
> Having such a public statement that anyone can see and people can
> point to is another weapon to help people fight the FUD that exists
> around Linux.
The whole article explains why apis are change for very good reasons
(evolution of hardware, security, we now know better, etc.) That's the
whole point of the document...
thanks,
greg k-h
next prev parent reply other threads:[~2008-02-03 5:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 14:44 [PATCH] Improve Documentation/stable_api_nonsense.txt v2 Heikki Orsila
2008-02-03 0:22 ` Greg KH
2008-02-03 0:52 ` Daniel Hazelton
2008-02-03 5:03 ` Greg KH [this message]
2008-02-03 5:53 ` Daniel Hazelton
2008-02-03 10:44 ` Heikki Orsila
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=20080203050310.GA23824@kroah.com \
--to=greg@kroah.com \
--cc=ak@suse.de \
--cc=dhazelton@enter.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m-ikeda@ds.jp.nec.com \
--cc=minchan.kim@gmail.com \
--cc=mpm@selenic.com \
--cc=shdl@zakalwe.fi \
--cc=zhongyu@18mail.cn \
/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