From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
"Robert P. J. Day" <rpjday@mindspring.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: maturity and status and attributes, oh my!
Date: Sat, 01 Sep 2007 16:27:28 +0200 [thread overview]
Message-ID: <46D976D0.7030208@s5r6.in-berlin.de> (raw)
In-Reply-To: <200709011544.07732.bzolnier@gmail.com>
Bartlomiej Zolnierkiewicz wrote:
...
> Part of the problem is that many people (including developers) learn about
> things being deprecated/obsoleted after they are actually removed.
>
> Of course things are not black and white and common sense is required but
> moving in the Kconfig direction is an improvement IMO and could speed up
> the development in the long-term.
...
I basically agree. Most people use precompiled kernel packages though.
For them we add kernel log messages, for example. We also preemptively
get in touch with user mailinglists and the like, but we reach only a
fraction of affected people there either.
For people who actually compile kernels, especially distributors, it
would indeed be helpful if "make oldconfig" and Co. show a prompt if an
option entered feature removal schedule. Actually this has been done
before for things like particular sysfs changes, with ad-hoc CONFIG_
variables.
--
Stefan Richter
-=====-=-=== =--= ----=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-09-01 14:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 21:38 Robert P. J. Day
2007-08-31 22:02 ` Jeff Garzik
2007-09-01 6:35 ` Jan Engelhardt
2007-09-01 9:06 ` Robert P. J. Day
2007-08-31 22:36 ` Stefan Richter
2007-09-01 1:23 ` Robert P. J. Day
2007-09-01 9:14 ` Stefan Richter
2007-09-01 9:21 ` Robert P. J. Day
2007-09-01 9:47 ` Stefan Richter
2007-09-01 9:54 ` Robert P. J. Day
2007-09-01 13:14 ` Jan Engelhardt
2007-09-01 13:53 ` Jeff Garzik
2007-09-01 10:43 ` Jeff Garzik
2007-09-01 10:52 ` Robert P. J. Day
2007-09-01 11:06 ` Jeff Garzik
2007-09-01 13:44 ` Bartlomiej Zolnierkiewicz
2007-09-01 13:52 ` Jeff Garzik
2007-09-01 14:27 ` Stefan Richter [this message]
[not found] ` <Pine.LNX.4.64.0709010435070.26137@localhost.localdomain>
2007-09-01 9:27 ` Stefan Richter
2007-09-01 9:41 ` Robert P. J. Day
2007-09-01 17:22 ` Dave Jones
2007-09-01 17:58 ` Robert P. J. Day
2007-09-01 18:06 ` Robert P. J. Day
2007-09-01 18:24 ` Dave Jones
2007-08-31 23:02 ` Dave Jones
2007-09-01 8:34 ` Robert P. J. Day
2007-08-31 23:29 Mitchell Erblich
2007-09-01 1:33 ` Robert P. J. Day
2007-09-01 6:39 ` Jan Engelhardt
2007-09-01 7:02 ` Robert P. J. Day
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=46D976D0.7030208@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=bzolnier@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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®