All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Upgrade chrpath and libevent
Date: Fri, 23 Dec 2011 09:42:57 -0800	[thread overview]
Message-ID: <4EF4BDA1.2060906@intel.com> (raw)
In-Reply-To: <cover.1324661415.git.scott.a.garman@intel.com>

On 12/23/2011 09:31 AM, Scott Garman wrote:
> Hello,
>
> This pull request upgrades the chrpath and libevent recipes. It has
> been build-tested on all 5 of our qemu architectures.

Please hold off on accepting this pull request. I forgot to include the 
distro tracking field updates, and when I just went to do so, I noticed 
that libevent had a NO_UPDATE_REASON field suggesting that libevent2 was 
not compatible. Which means I have to do a lot more testing on this 
before I can feel comfortable submitting it.

I will likely not get to this until I return on January 2.

Scott

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



  parent reply	other threads:[~2011-12-23 17:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 17:31 [PATCH 0/2] Upgrade chrpath and libevent Scott Garman
2011-12-23 17:31 ` [PATCH 1/2] chrpath: upgrade to 0.14 Scott Garman
2011-12-23 17:31 ` [PATCH 2/2] libevent: upgrade to 2.0.16 Scott Garman
2011-12-23 17:42 ` Scott Garman [this message]
2011-12-26 21:12   ` [PATCH 0/2] Upgrade chrpath and libevent Scott Garman
2011-12-28 18:37     ` Saul Wold
2011-12-29 15:05       ` Scott Garman
2011-12-29 15:28         ` Paul Eggleton
2011-12-29 20:42           ` Scott Garman
2011-12-29 22:06             ` Paul Eggleton
2012-01-04  0:02 ` 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=4EF4BDA1.2060906@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 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.