From: Andrew Morton <akpm@osdl.org>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reduce __deprecated spew
Date: Mon, 14 Mar 2005 22:42:21 -0800 [thread overview]
Message-ID: <20050314224221.442570a8.akpm@osdl.org> (raw)
In-Reply-To: <20050315063436.GN32638@waste.org>
Matt Mackall <mpm@selenic.com> wrote:
>
> This patch changes a couple of the noisier deprecations to only warn
> on the primary entrypoint (in these cases, the _register functions).
> This approach makes it obvious that an interface is going away while
> only warning once per user. I suggest we adopt this approach for
> future deprecation campaigns.
But that's going to warn when the deprecated function itself is compiled,
isn't it?
If so, that's backwards. We want to warn when the deprecated function is
_used_, so people go fix up their code, and we can then remove the
deprecated function.
(The intermodule_register and pm_register stuff has been hanging around for
so long that one wonders if we need sterner stimuli, not lesser).
next prev parent reply other threads:[~2005-03-15 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 6:34 Matt Mackall
2005-03-15 6:42 ` Andrew Morton [this message]
2005-03-15 7:16 ` Arjan van de Ven
2005-03-15 13:38 ` Josh Boyer
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=20050314224221.442570a8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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®