From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
"Robert P. J. Day" <rpjday@mindspring.com>
Subject: Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.
Date: Tue, 20 Feb 2007 19:42:50 +0100 [thread overview]
Message-ID: <200702201942.50186.bzolnier@gmail.com> (raw)
In-Reply-To: <45DB218E.1080106@imap.cc>
On Tuesday 20 February 2007 17:27, Tilman Schmidt wrote:
> On Sun, 18 Feb 2007 19:35:07 +0100, Bartlomiej Zolnierkiewicz wrote:
> > I think that the patch is useful and that the distinction between
> > DEPRECATED and OBSOLETE options is quite clear:
> >
> > * DEPRECATED == new better code is available, old code scheduled for removal
> >
> > * OBSOLETE == no replacement yet but the code is broken by design
> > and unreliable, not scheduled for removal yet
>
> Is that really the consensus on these definitions? I thought it was
> more or less the opposite:
>
> * DEPRECATED == no (complete) replacement available yet, but it has
> been decided that this code is less than optimal and alternatives
> should be preferred
>
> * OBSOLETE == replacement available, no reason to use this code anymore
Indeed, this way it makes more sense for me but I'll leave the definitive
answer to a native speaker(s).
Bart
next prev parent reply other threads:[~2007-02-20 18:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 17:06 [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE Robert P. J. Day
2007-02-18 18:35 ` Bartlomiej Zolnierkiewicz
2007-02-18 18:53 ` Robert P. J. Day
2007-02-20 16:27 ` Tilman Schmidt
2007-02-20 18:42 ` Bartlomiej Zolnierkiewicz [this message]
2007-02-20 22:52 ` Robert P. J. Day
2007-02-20 23:12 ` Tilman Schmidt
2007-02-20 23:23 ` Robert P. J. Day
2007-02-25 10:42 ` Pavel Machek
2007-02-25 22:59 ` Tilman Schmidt
2007-02-20 22:47 ` Robert P. J. Day
2007-02-20 22:56 ` Sam Ravnborg
2007-02-20 23:01 ` 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=200702201942.50186.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=tilman@imap.cc \
--cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.