From: "Jeff Ozvold" <jeffozvold@earthlink.net>
To: linux-hotplug@vger.kernel.org
Subject: <, > versus <=, >=
Date: Wed, 21 Mar 2001 04:50:48 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98514983327070@msgid-missing> (raw)
It seems to me that major changes happen on release boundaries; in Matt's
example, on the 3.00 boundary. Many compatibility changes happen for
"pre-version X.XX" versus "version X.XX and later."
If that's true, why not use < (less than) and >= (greater than or equal),
since it seems that it would fit the convention that we use when deploying
releases. It also avoids the problem of modifying earlier releases. For
example, we could write a rule that uses " < 2.4.0 " and ">= 2.4.0", so that
after 2.4.0 is released, we could release 2.2.19, 2.2.94733, etc, and we
don't have to change the rule (of course, as long as the functionality of
2.2.X doesn't change). We also avoid the problem of either duplicating or
not considering the "=" case.
A random thought?
-Jeff
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2001-03-21 4:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-hotplug-98514983327070@msgid-missing \
--to=jeffozvold@earthlink.net \
--cc=linux-hotplug@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 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).