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] Updating patch Upstream-Status
Date: Wed, 13 Jul 2011 12:25:42 +0100 [thread overview]
Message-ID: <1310556342.20015.1107.camel@rex> (raw)
In-Reply-To: <cover.1310521783.git.sgw@linux.intel.com>
On Tue, 2011-07-12 at 19:23 -0700, Saul Wold wrote:
> Richard,
>
> This cleans up some inconistent Upstream-Status: statuses along with some
> duplicate entries. I will have another batch soon with more Upstream-Status
> info, we have under 200 patches remaining with no status.
>
> Thanks
> Sau!
>
>
> The following changes since commit a6e9edb7b4b5b0bdb067a59d691d33fba8948963:
>
> sato-sdk: add clutter for sato-sdk image (2011-07-12 15:23:35 +0100)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib sgw/fix
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/fix
>
> Saul Wold (1):
> Patches: Fix Upstream-Status info
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-07-13 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 2:23 [PATCH 0/1] Updating patch Upstream-Status Saul Wold
2011-07-13 2:23 ` [PATCH 1/1] Patches: Fix Upstream-Status info Saul Wold
2011-07-13 11:25 ` 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=1310556342.20015.1107.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