Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: 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:36:30 -0700	[thread overview]
Message-ID: <4D94E5CE.3010801@mentor.com> (raw)
In-Reply-To: <20110331180721.GD23178@denix.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/31/2011 11:07 AM, 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
> 
> The machine commits were reordered to add kernel and u-boot recipes before the 
> actual machine configs.
> 
> 
> Pull URL: git://arago-project.org/git/people/denix/openembedded.git
>   Branch: 2011.03-maintenance
>   Browse: http://arago-project.org/git/people/?p=denix/openembedded.git;a=shortlog;h=refs/heads/2011.03-maintenance
> 
> Thanks,
>     Denys Dmytriyenko <denys@ti.com>
> ---
> 
> 
> Chase Maupin (6):
>   linux-omap3: add PSP recipe for am387x-evm
>   u-boot: Add PSP version for am387x-evm
>   sort: Add ti814x machine types
>   ti814x: Add new machine definitions
>   am-benchmarks: Add support for am387x-evm machine
>   matrix-gui: Add support for am387x-evm machine
> 
> Denys Dmytriyenko (2):
>   external-toolchain-angstrom: don't stage .la files
>   qt4: security advisory - blacklist fraudulent comodo certificates

Applied, thanks.

- -- 
Tom Rini
Mentor Graphics Corporation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNlOXOAAoJEI4NMjfc3nJxtzoIAKvyaue1FpcI8KiRCDADIsqH
hp3bS7R2XSymVqj13NGXjRzZsjAZcwK1gwFYiHsoLDvTg8Zbq3MNB6YuTBqYrN5h
ZbpzuG8RGuFvTONGlTCaQRluh+82nk6w3M2oqejGua9NcENu1fnfgC+jTy1K38v6
yzF4zOYDCP62DbJFW/VUf3X7TY5qrRdAl8DazkSJ4pXRDXTqYYbaWLdbmAvYMSPK
vnpyesWKv8etkWHgOIIGqwBQGnA9Db5Qnlya0QU/VqpGqzPLprnJkirrHShGq2GL
8YXnMffsAdqiaB0KL0da3wlL5UEc3H2qGrBqz/171btgYjx3ZpiCkMtGbAbTSx0=
=sD4J
-----END PGP SIGNATURE-----



  reply	other threads:[~2011-03-31 20:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 18:07 [2011.03-maintenance] Pull request for new TI machines, angstrom and qt4 fixes Denys Dmytriyenko
2011-03-31 20:36 ` Tom Rini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-31  7:45 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

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=4D94E5CE.3010801@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox