From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] i2c-tools: Remove superseded i2c-tools 3.0.1.
Date: Mon, 16 Nov 2009 06:35:42 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911160632490.24057@localhost> (raw)
In-Reply-To: <4B01352A.6070808@kernelconcepts.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1348 bytes --]
On Mon, 16 Nov 2009, Florian Boor wrote:
> Hi,
>
> Robert P. J. Day schrieb:
> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> I do not agree on this. There is no way to make sure people are not
> using it. Even if it is unlikely the new release might break for
> some of our users or just rely on something that is not available
> for everyone. Apart from this I do not see much of a reason for
> removing it at all.
by the way, i did check the changelog first to see if the
enhancements were useful enough to warrant upgrading. the changelog:
http://linux.softpedia.com/progChangelog/I2C-Tools-Changelog-31650.html
What's new in I2C Tools 3.0.2:
· Error handling has been improved.
· Buses can now be passed by name.
· A compatibility issue with perl 5.10.0 has been fixed.
that struck me as sufficiently useful to warrant an upgrade, but maybe
not.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
prev parent reply other threads:[~2009-11-16 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 16:55 [PATCH] i2c-tools: Remove superseded i2c-tools 3.0.1 Robert P. J. Day
2009-11-16 11:19 ` Florian Boor
2009-11-16 11:30 ` Robert P. J. Day
2009-11-16 12:09 ` Florian Boor
2009-11-16 11:35 ` Robert P. J. Day [this message]
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=alpine.LFD.2.00.0911160632490.24057@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.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.