From: Khem Raj <raj.khem@gmail.com>
To: "Osier-mixon, Jeffrey" <jeffrey.osier-mixon@intel.com>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>,
"Wold, Saul" <saul.wold@intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Upstream-Status finally @ 100%
Date: Wed, 8 Feb 2012 09:45:05 -0800 [thread overview]
Message-ID: <CAMKF1spwxYzxRM2NbYfaU_GLXqjBtuXi5kO_Up6t2MS1zREi4g@mail.gmail.com> (raw)
In-Reply-To: <CALZ2gZX3LMTcJ11qg5T7RAJRGpcR3fE0YB2cWMbmXPzo3Vpqqg@mail.gmail.com>
On Wed, Feb 8, 2012 at 9:34 AM, Osier-mixon, Jeffrey
<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
WARNING: multiple messages have this Message-ID (diff)
From: Khem Raj <raj.khem@gmail.com>
To: "Osier-mixon, Jeffrey" <jeffrey.osier-mixon@intel.com>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>,
"Wold, Saul" <saul.wold@intel.com>,
"Stewart, David C" <david.c.stewart@intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] Upstream-Status finally @ 100%
Date: Wed, 8 Feb 2012 09:45:05 -0800 [thread overview]
Message-ID: <CAMKF1spwxYzxRM2NbYfaU_GLXqjBtuXi5kO_Up6t2MS1zREi4g@mail.gmail.com> (raw)
In-Reply-To: <CALZ2gZX3LMTcJ11qg5T7RAJRGpcR3fE0YB2cWMbmXPzo3Vpqqg@mail.gmail.com>
On Wed, Feb 8, 2012 at 9:34 AM, Osier-mixon, Jeffrey
<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
next prev parent reply other threads:[~2012-02-08 17:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 9:11 Upstream-Status finally @ 100% Saul Wold
2012-02-08 9:11 ` 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 [this message]
2012-02-08 17:45 ` 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=CAMKF1spwxYzxRM2NbYfaU_GLXqjBtuXi5kO_Up6t2MS1zREi4g@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=jeffrey.osier-mixon@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.com \
--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.