All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [2011.03-maintenance] Pull request for new TI machines, angstrom and qt4 fixes
Date: Thu, 31 Mar 2011 13:40:33 -0400	[thread overview]
Message-ID: <20110331174033.GC23178@denix.org> (raw)
In-Reply-To: <4D94AF84.8020000@mentor.com>

On Thu, Mar 31, 2011 at 09:44:52AM -0700, Tom Rini wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 03/31/2011 02:10 AM, Koen Kooi wrote:
> > On 31-03-11 09:45, Denys Dmytriyenko wrote:
> >> Tom,
> > 
> >> Please pull these 8 commits for the external Angstrom toolchain fix,
> >> qt4 security advisory fix, as well as for addition of new TI machines.
> >> All are cherry picked from oe.dev
> > 
> > Merging it like this creates a few broken commits because the machines
> > were added first. Is that really what we want?
> 
> We do not.  Denys, please re-order the commits so that things are
> building in each commit.  Thanks!

Done. Please check the same tree and branch. Or do you want me to send a new 
pull request?

-- 
Denys



  reply	other threads:[~2011-03-31 18:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31  7:45 [2011.03-maintenance] Pull request for new TI machines, angstrom and qt4 fixes Denys Dmytriyenko
2011-03-31  9:10 ` Koen Kooi
2011-03-31 10:51   ` Frans Meulenbroeks
2011-03-31 11:04     ` Koen Kooi
2011-03-31 11:57       ` Frans Meulenbroeks
2011-03-31 12:36         ` Philip Balister
2011-03-31 16:47     ` Tom Rini
2011-03-31 20:28       ` Frans Meulenbroeks
2011-03-31 16:44   ` Tom Rini
2011-03-31 17:40     ` Denys Dmytriyenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-31 18:07 Denys Dmytriyenko
2011-03-31 20:36 ` Tom Rini

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=20110331174033.GC23178@denix.org \
    --to=denis@denix.org \
    --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.