From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: RFC: fortran-2.eclass - Support for bin package system without compiler
Date: Thu, 18 Jul 2013 08:25:59 +0000 (UTC) [thread overview]
Message-ID: <pan$3c2f4$f4a3b62d$27d9b8c5$3faded84@cox.net> (raw)
In-Reply-To: 51E79931.5040206@gentoo.org
Justin posted on Thu, 18 Jul 2013 09:28:49 +0200 as excerpted:
> + case ${EAPI:-0} in
> + 0|1|2|3)
> + eqawarn "The fortran-2.eclass is going to deprecate support
^^^^^^^^^^^
That reads strange to me. Deprecated doesn't mean it no longer works; it
means it's declared obsolete and recommended against but it still works
for now, thus giving users a time to migrate.[1]
So "is going to deprecate" seems strange. It should be "has deprecated",
or rewording a bit more "support is deprecated for" or the like. Because
by the time someone's actually reading that output, the warning is
already there; the deprecation has already happened.
Alternatively, keep the future tense and say "will be removed" or some
such, or use a hybrid, "support is deprecated and will be removed".
---
[1] deprecate/deprecation online references:
http://en.wiktionary.org/wiki/deprecate
https://en.wikipedia.org/wiki/Deprecation
http://www.thefreedictionary.com/deprecate
http://www.google.com/search?q=define:deprecate
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-07-18 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 7:07 [gentoo-dev] RFC: fortran-2.eclass - Support for bin package system without compiler Justin
2013-07-18 7:12 ` Michał Górny
2013-07-18 7:28 ` Justin
2013-07-18 8:25 ` Duncan [this message]
2013-07-18 8:44 ` [gentoo-dev] " Justin
2013-07-18 15:39 ` Donnie Berkholz
2013-07-18 15:50 ` Justin
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='pan$3c2f4$f4a3b62d$27d9b8c5$3faded84@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox