From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Upstream-Status: Update for some GPLv2 patch, edwin, May17, 2011
Date: Tue, 17 May 2011 14:58:19 +0100 [thread overview]
Message-ID: <1305640699.3424.237.camel@rex> (raw)
In-Reply-To: <cover.1305639192.git.edwin.zhai@intel.com>
On Tue, 2011-05-17 at 21:36 +0800, Zhai Edwin wrote:
> From: Zhai Edwin <edwin.zhai@intel.com>
>
> Saul,
> Upstream-Status for some GPLv2 patches including gzip and mtools.
>
> Thanks,
> edwin
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: gzhai/fix3
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=gzhai/fix3
>
> Thanks,
> Zhai Edwin <edwin.zhai@intel.com>
> ---
>
>
> Zhai Edwin (1):
> Upstream-Status: Update patch upstream-status for GPLv2 recipes
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-05-17 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 13:36 [PATCH 0/1] Upstream-Status: Update for some GPLv2 patch, edwin, May17, 2011 Zhai Edwin
2011-05-17 13:36 ` [PATCH 1/1] Upstream-Status: Update patch upstream-status for GPLv2 recipes Zhai Edwin
2011-05-17 13:58 ` Richard Purdie [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=1305640699.3424.237.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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