From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Robert P. J. Day" Subject: Re: i2c-tools 4.0 Date: Thu, 10 Aug 2017 14:19:56 -0400 (EDT) Message-ID: References: <20170803153414.4c9135ff@endymion> <20170810095936.22a8057a@endymion> <1502357367.6201.9.camel@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Return-path: Received: from cpanel2.indieserve.net ([199.212.143.6]:43858 "EHLO cpanel2.indieserve.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752552AbdHJSUA (ORCPT ); Thu, 10 Aug 2017 14:20:00 -0400 In-Reply-To: <1502357367.6201.9.camel@suse.de> Sender: linux-i2c-owner@vger.kernel.org List-Id: linux-i2c@vger.kernel.org To: Jean Delvare Cc: Linux I2C , Wolfram Sang 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 ========================================================================