LKML Archive on
help / color / mirror / Atom feed
From: "Robert P. J. Day" <>
To: Jan Engelhardt <>
Cc: "H. Peter Anvin" <>,
	Linux kernel mailing list <>
Subject: Re: [PATCH] Introduce two new maturlty levels:  DEPRECATED and OBSOLETE.
Date: Thu, 18 Jan 2007 05:38:14 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0701180532070.8331@CPE00045a9c397f-CM001225dbafb6> (raw)
In-Reply-To: <Pine.LNX.4.61.0701181116250.19740@yvahk01.tjqt.qr>

On Thu, 18 Jan 2007, Jan Engelhardt wrote:

> >On Wed, 17 Jan 2007, H. Peter Anvin wrote:
> >
> >> DEPRECATED should presumably default to Y; OBSOLETE to n.
> >
> >crap, now i see what you were getting at -- i forgot to assign
> >defaults.  i'll resubmit, but i'll wait for anyone to suggest any
> >better help content if they have a better idea.
> Well... _maybe_ documentation/scheduled-removal.txt (or whatever it
> is called) could now be merged into the kconfig options and help
> text. Or maybe not, to keep it easy to track deprecated code.
> Well, even if scheduled-removal.txt stays, you could submit a 2nd
> patch putting OBSOLETE and DEPRECATED tags to the Kconfig options
> listed in scheduled-removal.txt, so that kconfig+sched are in sync.

i'm assuming you mean "Documentation/feature-removal-schedule.txt".
that would *seem* to make sense, after only a few seconds of thought.
once config options are tagged with either DEPRECATED or OBSOLETE,
surely it wouldn't be hard to be able to pull out a list of those from
the source tree, based on their Kconfig dependencies.

but, again, that's getting ahead of ourselves.  certainly, it's
something that *could* be done at some point, but not knowing exactly
how one would do that doesn't stop anyone from adding those two config
settings *now*, just to get the process rolling.

let's not over-analyze this too much.


p.s.  it might be worth perusing the feature removal file, to see what
features are still listed there even though they were scheduled to be
removed some time ago.  just a thought.

      reply	other threads:[~2007-01-18 10:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17 21:21 Robert P. J. Day
2007-01-17 21:55 ` H. Peter Anvin
2007-01-17 21:56 ` H. Peter Anvin
2007-01-17 22:05   ` Robert P. J. Day
2007-01-17 22:07   ` Robert P. J. Day
2007-01-18 10:18     ` Jan Engelhardt
2007-01-18 10:38       ` Robert P. J. Day [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0701180532070.8331@CPE00045a9c397f-CM001225dbafb6 \ \ \ \ \
    --subject='Re: [PATCH] Introduce two new maturlty levels:  DEPRECATED and OBSOLETE.' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).