From: Saul Wold <saul.wold@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Yocto Project Discussion <yocto@yoctoproject.org>,
'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>
Subject: Upstream-Status finally @ 100%
Date: Wed, 08 Feb 2012 01:11:46 -0800 [thread overview]
Message-ID: <4F323C52.8030304@intel.com> (raw)
We finally did it!
After getting some final patches yesterday, we made it to 100% with
patch Upsteam-Status.
Total Patches Files: 1243
All Upstream-Status: 1243
Fix Upstream-Status: 0
Need Upstream-Status: 0
Pending Upstream-Status: 461
This means we have 461 patches to now work their way into the Upstream
communities.
Let's work to maintain this, I will be watching incoming patches and
using a check script to verify that patches have Upstream-Status.
Thanks to all those people who worked to get Upstream-Status into their
patches.
Sau!
WARNING: multiple messages have this Message-ID (diff)
From: Saul Wold <saul.wold@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Yocto Project Discussion <yocto@yoctoproject.org>,
'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>
Cc: "Stewart, David C" <david.c.stewart@intel.com>
Subject: Upstream-Status finally @ 100%
Date: Wed, 08 Feb 2012 01:11:46 -0800 [thread overview]
Message-ID: <4F323C52.8030304@intel.com> (raw)
We finally did it!
After getting some final patches yesterday, we made it to 100% with
patch Upsteam-Status.
Total Patches Files: 1243
All Upstream-Status: 1243
Fix Upstream-Status: 0
Need Upstream-Status: 0
Pending Upstream-Status: 461
This means we have 461 patches to now work their way into the Upstream
communities.
Let's work to maintain this, I will be watching incoming patches and
using a check script to verify that patches have Upstream-Status.
Thanks to all those people who worked to get Upstream-Status into their
patches.
Sau!
next reply other threads:[~2012-02-08 9:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 9:11 Saul Wold [this message]
2012-02-08 9:11 ` Upstream-Status finally @ 100% Saul Wold
2012-02-08 10:07 ` Björn Stenberg
2012-02-08 18:57 ` Saul Wold
2012-02-08 21:26 ` Daniel Stenberg
2012-02-08 21:34 ` Khem Raj
2012-02-08 23:18 ` Saul Wold
2012-02-09 9:26 ` Daniel Stenberg
2012-02-09 12:22 ` Koen Kooi
2012-02-09 12:30 ` Paul Eggleton
2012-02-09 14:51 ` Koen Kooi
2012-02-09 15:31 ` Paul Eggleton
2012-02-09 17:39 ` Saul Wold
2012-02-09 14:46 ` Khem Raj
2012-02-08 19:23 ` Khem Raj
2012-02-08 17:07 ` Stewart, David C
2012-02-08 17:34 ` Osier-mixon, Jeffrey
2012-02-08 17:37 ` Paul Eggleton
2012-02-08 17:37 ` [yocto] " Paul Eggleton
2012-02-08 17:45 ` Khem Raj
2012-02-08 17:45 ` [yocto] " Khem Raj
2012-02-08 18:04 ` Osier-mixon, Jeffrey
2012-02-08 18:45 ` Saul Wold
2012-02-08 18:45 ` [yocto] " Saul Wold
2012-02-08 21:44 ` [OE-core] " Paul Menzel
2012-02-08 21:44 ` Paul Menzel
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=4F323C52.8030304@intel.com \
--to=saul.wold@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto@yoctoproject.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.