From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Jean Delvare <jdelvare@suse.de>
Cc: Linux I2C <linux-i2c@vger.kernel.org>, Wolfram Sang <wsa@the-dreams.de>
Subject: Re: i2c-tools 4.0
Date: Thu, 10 Aug 2017 14:19:56 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1708101417120.9961@localhost.localdomain> (raw)
In-Reply-To: <1502357367.6201.9.camel@suse.de>
On Thu, 10 Aug 2017, Jean Delvare wrote:
> On jeu., 2017-08-10 at 04:30 -0400, Robert P. J. Day wrote:
> > On Thu, 10 Aug 2017, Jean Delvare wrote:
> > > Thanks for the report. I wonder why people always wait for
> > > announcements of imminent releases to report bugs ;-) Bugs have to
> > > be fixed anyway, before or after a release doesn't really make a
> > > difference, as there were other releases before and there will be
> > > other releases later. Distributions will cherry pick individual
> > > commits for backport as needed.
> >
> > i actually did ask about this very issue last month:
> >
> > http://marc.info/?l=linux-i2c&m=150109384702585&w=2
>
> You forgot to Cc me :(
in my defense, at the time, the README file knew nothing about you.
:-)
http://marc.info/?l=linux-i2c&m=150092316304021&w=2
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2017-08-10 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 13:34 i2c-tools 4.0 Jean Delvare
2017-08-07 21:06 ` Wolfram Sang
2017-08-08 17:59 ` Robert P. J. Day
2017-08-10 7:59 ` Jean Delvare
2017-08-10 8:30 ` Robert P. J. Day
2017-08-10 9:29 ` Jean Delvare
2017-08-10 18:19 ` Robert P. J. Day [this message]
2017-10-12 11:42 ` Ondřej Lysoněk
2017-10-19 15:00 ` 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=alpine.LFD.2.20.1708101417120.9961@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).