All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
	<openembedded-devel@lists.openembedded.org>
Subject: confused about where i2c-tools-3.0.2 came from
Date: Thu, 19 Nov 2009 04:42:19 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0911190430300.3527@localhost> (raw)


  i'm puzzled -- only a few days ago, i was proposing updating the
i2c-tools package from 3.0.1 to 3.0.2 in the dev branch.  there was a
brief discussion that i shouldn't simply *remove* the 3.0.1 contents,
just *add* what was needed for 3.0.2.

  i came back to do that this morning and there already *is*
everything needed for 3.0.2 -- the conf/checksums.ini entry and the
.bb file.  now i check the git log file for conf/checksums.ini and i
find:

commit b3a5d14572d3ddf13e740f32a463afb7e6a2dc58
Author: Koen Kooi <koen@openembedded.org>
Date:   Tue Dec 16 14:50:47 2008 +0100

    i2c-tools: update to 3.0.2

  i could have *sworn* 3.0.2 wasn't in my checkout of the dev branch,
or i wouldn't have put any time into proposing an upgrade.  how
confused am i?  how could i have not noticed that?

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================



                 reply	other threads:[~2009-11-19  9:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.0911190430300.3527@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.