Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [2011.03-maintenance] Pull request #15
Date: Mon, 25 Apr 2011 09:48:28 -0700	[thread overview]
Message-ID: <4DB5A5DC.5040701@mentor.com> (raw)
In-Reply-To: <ioru67$bfr$1@dough.gmane.org>

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

On 04/22/2011 06:00 AM, Koen Kooi wrote:
> Tom,
> 
> Please pull the 18 commits from here:
> 
> URI: git://dominion.thruhere.net/var/cache/git/openembedded.git
> Branch: 2011.03-maintenance
> 
> Eyal Reizer (3):
>       ti-wifi-utils: update to a newer git commit
>       hostap-daemon: build from git sources
>       wpa-supplicant: Build from git sources
> 
> Koen Kooi (1):
>       libgles-omap3: abstract ES handling and share it across all
> 
> Tom Rini (14):
>       db: Rework arm-thumb-mutex_db5.patch
>       db: Switch to patchdir rather than applying in do_configure
>       ftpd-topfield: Rework usb-header-name-2-6-23.patch
>       opie-sh 1.2.4: Rework opie-sh-fsmounter-name.patch
>       qscintilla 1.65-gpl-1.6: Rework no-external-lexers.patch
>       poboxserver: Rework unicode.patch
>       xqt2: Rework the patches for xqt2 (vs the core part).
>       In a large number of patches, remove unneeded '..' in paths.
>       opie-sh: Switch to patchdir rather than applying in do_configure
>       poboxserver: Switch to patchdir rather than applying in
>       qscintilla: Switch to patchdir rather than applying in
>       xqt2: Switch to patchdir rather than applying in do_configure
>       samba: Switch to patchdir rather than applying in do_configure
>       vim: Switch to patchdir rather than applying in do_configure
> 
> These are all cherry-picks from .dev.
> 
> regards,
> 
> Koen

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/

iQEcBAEBAgAGBQJNtaXWAAoJEI4NMjfc3nJx+XIIAJD7wJuTToZ4ixXPhubEFG0z
v4E8PsL6GqP2B7XDwSae54CZnEGFWjwrjg1TbTT481BkofE8xyE0ifoP7n9VIqJi
qcl1eaIVyN7p76RDy3LJgHOG6K0DhNHlRtEEK52fU73EorGYGiJApN/2eiSxLw2q
nMvIxWvMUXGjEMJ6k7EZNII8iudNENGM5eAdcv9loeua32i/pDmAjGhlmm4JUMwb
PvV+ZSByNvCRjppCH/nlsCPorSKgX1JQmUty33Jt76LiRIsrIykCpqoHvoXYQUOG
kCGRZEBeQ+K6a8OMYSJopEuk3c0qGd0si0yPdHacTdzeSbLr3tAUTm+QFWls9YI=
=cMaR
-----END PGP SIGNATURE-----



      reply	other threads:[~2011-04-25 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-22 13:00 [2011.03-maintenance] Pull request #15 Koen Kooi
2011-04-25 16:48 ` Tom Rini [this message]

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=4DB5A5DC.5040701@mentor.com \
    --to=tom_rini@mentor.com \
    --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