From: Saul Wold <saul.wold@intel.com>
To: "Osier-mixon, Jeffrey" <jeffrey.osier-mixon@intel.com>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
"Stewart, David C" <david.c.stewart@intel.com>
Subject: Re: [yocto] Upstream-Status finally @ 100%
Date: Wed, 08 Feb 2012 10:45:07 -0800 [thread overview]
Message-ID: <4F32C2B3.7020200@intel.com> (raw)
In-Reply-To: <CALZ2gZWmpnhxg=aa3qLbrpQLJqfgOn2W5WH0369rdHqyKqaD-A@mail.gmail.com>
On 02/08/2012 10:04 AM, Osier-mixon, Jeffrey wrote:
> Ah, documentation :) excellent
>
Jefro:
You can get more info about this from Mark's OE page:
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
The Key thing to note on my numbers is that we have 461 patches that
could potentially be up-streamed to other communities, depending the
status of those communities, from active communities accepting patches
to upstream source that is just download-able with no activity or
maintainers.
We have 1243 patches overall, which include OE Specific configuration
patches and Embedded specific tweaks to various upstreams that may not
be appropriate or acceptable to the upstream community.
Sau!
> On Wed, Feb 8, 2012 at 9:45 AM, Khem Raj <raj.khem@gmail.com
> <mailto:raj.khem@gmail.com>> wrote:
>
> On Wed, Feb 8, 2012 at 9:34 AM, Osier-mixon, Jeffrey
> <jeffrey.osier-mixon@intel.com
> <mailto:jeffrey.osier-mixon@intel.com>> wrote:
> > This sounds fantastic, and I'd love to create a page on the website
> > reflecting this. Just so I am clear, what exactly is this 100%
> of? Do we
> > have no local patches to upstream projects at all?
>
> it means that all patches have a field 'Upstream-Status'
> and for most of them it reflects the status of patch w.r.t. upstream
> of given package
>
>
>
>
> --
> Jeff Osier-Mixon http://jefro.net/blog
> Yocto Project Community Manager @Intel http://yoctoproject.org
> <http://yoctoproject.org/>
>
next prev parent reply other threads:[~2012-02-08 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 9:11 Upstream-Status finally @ 100% Saul Wold
[not found] ` <CDED78A957032E45B3239CDDA7642D1508437968@ORSMSX105.amr.corp.intel.com>
[not found] ` <CALZ2gZX3LMTcJ11qg5T7RAJRGpcR3fE0YB2cWMbmXPzo3Vpqqg@mail.gmail.com>
2012-02-08 17:37 ` [yocto] " Paul Eggleton
2012-02-08 17:45 ` Khem Raj
[not found] ` <CALZ2gZWmpnhxg=aa3qLbrpQLJqfgOn2W5WH0369rdHqyKqaD-A@mail.gmail.com>
2012-02-08 18:45 ` Saul Wold [this message]
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=4F32C2B3.7020200@intel.com \
--to=saul.wold@intel.com \
--cc=david.c.stewart@intel.com \
--cc=jeffrey.osier-mixon@intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox