From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: devicetree spec mailing list <devicetree-spec@vger.kernel.org>
Subject: Definition of "should" seems inconsistent with idea of "deprecated"
Date: Thu, 19 Oct 2023 07:03:56 -0400 (EDT) [thread overview]
Message-ID: <cddc5065-42d2-11f6-9195-296361c8aef7@crashcourse.ca> (raw)
Reading DTSpec v0.4, near the beginning:
"The word should is used to indicate that among several possibilities
one is recommended as particularly suitable, without mentioning or
excluding others; or that a certain course of action is preferred but
not necessarily required; or that (in the negative form) a certain
course of action is deprecated but not prohibited (should equals is
recommended that)."
It seems contradictory to suggest that "should" implies
"recommended" but, in the negative sense, it can also support
"deprecated", which typically suggests something that is *not*
recommended but is nonetheless acceptable.
It just seems like that's giving off mixed messages.
rday
next reply other threads:[~2023-10-19 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 11:03 Robert P. J. Day [this message]
2023-10-19 23:33 ` Definition of "should" seems inconsistent with idea of "deprecated" David Gibson
2023-10-21 9:08 ` Robert P. J. Day
2023-10-23 0:32 ` David Gibson
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=cddc5065-42d2-11f6-9195-296361c8aef7@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--cc=devicetree-spec@vger.kernel.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.