From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Call for 2.10.3
Date: Sun, 04 Mar 2007 10:41:36 +0000 [thread overview]
Message-ID: <20070304114136.27150bee.khali@linux-fr.org> (raw)
In-Reply-To: <20070303171327.186cd0f4.khali@linux-fr.org>
Hi Hans,
Please keep the list in copy...
On Sun, 04 Mar 2007 01:24:25 +0100, Hans de Goede wrote:
> Jean Delvare wrote:
> > I fear we'll have to release 2.10.3 earlier than originally planed. The
> > sooner would be the better, in fact. Due to new i2c-core cleanups,
> > libsensors needs again to be updated to anticipate the kernel changes
> > and give our users (and distributions) a chance to upgrade user-space
> > before upgrading their kernel, so they won't break "sensors" and other
> > tools.
> >
> > There is no bugfix pending as far as I know. If anyone thinks something
> > in particular needs to be committed before we release 2.10.3, please
> > speak up.
> >
> > Release schedule could look like:
> > * March 11th: SVN freeze
> > * March 12th-18th: testing
> > * March 19th: release
> >
> > As there was no changes made to the i2c repository since 2.10.2, this
> > will be a lm_sensors-release only (not that it makes much difference
> > anyway).
>
> What about the:
> -dynamic sysfs chip support
> -get_sensor_type addition
> -generic print suppoty in sensors the program
>
> A previous group of my students has been worming on, any chance some of
> those could make it, or maybe that we can start looking at them after
> the 19th?
I discussed this with Mark M. Hoffman and we agreed that this was
lm-sensors 3.0 material. Mark is more or less in charge of the
lm-sensors 3.0 tree, while I'm taking care of the current "stable"
branch (2.10.x)
> Either way I'll give those students a kick telling them to get moving on
> getting their work presented here and integrated.
I agree that we are not very fair with your students which apprently
made a good job which we fail unfortunately failed to integrate
quickly. But well I can't work on everything at once, sorry. If you
want write access to the SVN repository to do it yourself, fine with
me, just ask.
--
Jean Delvare
next prev parent reply other threads:[~2007-03-04 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 16:13 [lm-sensors] Call for 2.10.3 Jean Delvare
2007-03-04 10:41 ` Jean Delvare [this message]
2007-03-04 11:15 ` Hans de Goede
2007-03-04 17:00 ` Mark M. Hoffman
2007-03-04 20:22 ` Hans de Goede
2007-03-15 6:56 ` Jean Delvare
2007-03-19 8:35 ` Jean Delvare
2007-03-19 18:12 ` Philip Edelbrock
2007-03-19 18:46 ` Jean Delvare
2007-03-25 15:03 ` 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=20070304114136.27150bee.khali@linux-fr.org \
--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.