Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] e2fsprogs streamlining
Date: Mon, 30 Jan 2012 18:49:47 -0800	[thread overview]
Message-ID: <4F2756CB.806@intel.com> (raw)
In-Reply-To: <cover.1327977970.git.scott.a.garman@intel.com>

On 01/30/2012 06:47 PM, Scott Garman wrote:
> Hello,
>
> Koen Kooi suggested that the quotefix patch was not needed,
> and the build of the recipe should now be multithread-safe.
> My testing has confirmed this.

Sorry, I forgot a PR bump - my branch will be updated with this momentarily.

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center



  parent reply	other threads:[~2012-01-31  2:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31  2:47 [PATCH 0/1] e2fsprogs streamlining Scott Garman
2012-01-31  2:47 ` [PATCH 1/1] e2fsprogs: remove unneeded patch and re-enable PARALLEL_MAKE Scott Garman
2012-01-31  2:49 ` Scott Garman [this message]
2012-02-02 17:57 ` [PATCH 0/1] e2fsprogs streamlining Saul Wold

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=4F2756CB.806@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox