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 2/2] distro_tracking: updates for upgraded recipes and manual checks
Date: Fri, 16 Mar 2012 09:35:58 -0700	[thread overview]
Message-ID: <4F636BEE.8040807@intel.com> (raw)
In-Reply-To: <08f07a7e59d7568f7588574b17a71d9852d1ef89.1331914572.git.scott.a.garman@intel.com>

On 03/16/2012 09:19 AM, Scott Garman wrote:
> Updates for upgraded recipes e2fsprogs and ...?

Whoops, just rebased my tree to eliminate that typo at the end.

Scott

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



  reply	other threads:[~2012-03-16 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 16:19 [PATCH 0/2] e2fsprogs and manual recipe checks updates Scott Garman
2012-03-16 16:19 ` [PATCH 1/2] e2fsprogs: upgrade to 1.42.1 Scott Garman
2012-03-16 16:19 ` [PATCH 2/2] distro_tracking: updates for upgraded recipes and manual checks Scott Garman
2012-03-16 16:35   ` Scott Garman [this message]
2012-03-21 18:48 ` [PATCH 0/2] e2fsprogs and manual recipe checks updates 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=4F636BEE.8040807@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