All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] lm-sensors 3.0.0-rc2 to be released soon
Date: Sun, 07 Oct 2007 09:31:11 +0000	[thread overview]
Message-ID: <20071007113111.2e0a275f@hyperion.delvare> (raw)

Hi all,

I plan to release lm-sensors 3.0.0-rc2 tomorrow or the day after. The
changes from rc1 are as follows (from CHANGES):

  Makefile: Add sensors-conf-convert to make install
  libsensors: Notify the caller when writing a value fails
              Differentiate between different read error types
              Report I/O errors as such
  sensord: Log the error code on failure
           Drop the configuration file search path mechanism (#2259)
           Manual page update
  sensors: Fix spurious critical temperature alarm
           Print error messages to stderr
           Make error messages more helpful and consistent
           Better handling of the fault flags
  sensors-conf-convert: Add a short help text
  sensors-detect: Fix SMSC SCH311x detection


I am not yet sure if this will be the last release candidate before the
final release. On the one hand, it seems to work really well, but on
the other hand I really would like at least one additional application
to be ported to the new libsensors API to confirm that it is OK.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

             reply	other threads:[~2007-10-07  9:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-07  9:31 Jean Delvare [this message]
2007-10-10 21:02 ` [lm-sensors] lm-sensors 3.0.0-rc2 to be released soon Jean Delvare
2007-10-11 16:28 ` Pinkel
2007-10-11 16:32 ` 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=20071007113111.2e0a275f@hyperion.delvare \
    --to=khali@linux-fr.org \
    --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.