Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/4] Bug fixing and code clarity
Date: Thu, 11 Aug 2011 20:01:47 -0700	[thread overview]
Message-ID: <1313118113.4708.0.camel@scimitar> (raw)
In-Reply-To: <1313106078.14274.476.camel@rex>

On Fri, 2011-08-12 at 00:41 +0100, Richard Purdie wrote:
> On Thu, 2011-08-11 at 15:58 -0700, Joshua Lock wrote:
> > On Wed, 2011-08-10 at 18:19 -0700, Joshua Lock wrote:
> > > The following series addresses some thinko/typo's I'd introduced to hob, by
> > > using variable names which are too similar, as well as adding some changes
> > > to increase clarity in various places.
> > 
> > This series rolled into a new series submitted just now, please ignore
> > this series.
> 
> I've actually already merged this series. Was there any change in the
> newer version I should be looking for?

None at all, I was just using the same branch to push the new changes so
included them in the new pull request.

Apologies for any confusion.

Joshua
-- 
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre




      reply	other threads:[~2011-08-12  3:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11  1:19 [PATCH 0/4] Bug fixing and code clarity Joshua Lock
2011-08-11  1:19 ` [PATCH 1/4] bb/ui/crumbs/tasklistmodel: fix some typos and add comments to mark() Joshua Lock
2011-08-11  1:19 ` [PATCH 2/4] bb/ui/crumbs/tasklistmodel: correctly uniquify dependency list Joshua Lock
2011-08-11  1:19 ` [PATCH 3/4] bb/ui/crumbs/tasklistmodel: don't include an item in its own depends Joshua Lock
2011-08-11  1:19 ` [PATCH 4/4] bb/cache: rename confusing variable Joshua Lock
2011-08-11 22:58 ` [PATCH 0/4] Bug fixing and code clarity Joshua Lock
2011-08-11 23:41   ` Richard Purdie
2011-08-12  3:01     ` Joshua Lock [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=1313118113.4708.0.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox