From: ppokorny@penguincomputing.com (Philip Pokorny)
To: lm-sensors@vger.kernel.org
Subject: Call for 2.8.0 soon
Date: Thu, 19 May 2005 06:23:59 +0000 [thread overview]
Message-ID: <3EE8A199.2040804@penguincomputing.com> (raw)
In-Reply-To: <3EE7C67A.4040703@paradyne.com>
Jean Delvare wrote:
>>>- libsensors numbering because of binary incompatibility..... go to
>>>1.5.0 or 2.0.0?
>>
>>What about going with 2.8.0... Then track the lm_sensors version.
>
>
> Why that? There is no reason we number the lib version according to the
> package version. The lib compatibility is unlikely to change that often.
Actually, it is.
Anytime a driver is added to the library, the library version needs to
change. This is because the library has compiled in code for every chip
that it knows about. And the sensors executable has references to every
chip that is supported by the matching libsensors.
I think the chances are high that at each release of lm_sensors, at
least one new driver will be added...
This is also part of my motivation for trying to remove this coupling in
the "rewrite" of libsensors...
:v)
--
Philip Pokorny, Director of Engineering
Tel: 415-358-2635 Fax: 415-358-2646 Toll Free: 888-PENGUIN
PENGUIN COMPUTING, INC.
www.penguincomputing.com
next prev parent reply other threads:[~2005-05-19 6:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:23 Call for 2.8.0 soon Mark D. Studebaker
2005-05-19 6:23 ` Philip Pokorny [this message]
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Philip Pokorny
2005-05-19 6:23 ` Mark D. Studebaker
2005-05-19 6:23 ` Greg KH
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jean Delvare
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=3EE8A199.2040804@penguincomputing.com \
--to=ppokorny@penguincomputing.com \
--cc=lm-sensors@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.