From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@beagleboard.org>
Cc: yocto@yoctoproject.org
Subject: Re: Upstream-Status finally @ 100%
Date: Thu, 09 Feb 2012 15:31:02 +0000 [thread overview]
Message-ID: <2515705.YAd3HxSNCM@helios> (raw)
In-Reply-To: <3FF9BD4A-F07C-4958-8758-9D4DC02171A0@beagleboard.org>
On Thursday 09 February 2012 15:51:11 Koen Kooi wrote:
> > The status ought to be correct with regard to the patch author's
> > assessment of whether or not the patch can go upstream.
>
> That's where I disagree, it's called 'Upstream-status', not
> 'Perceived-upstream-status'. The field should reflect the status from an
> upstream perspective, not from the OE perspective. So both 'Pending' and
> 'Inappropriate' boil down to 'Not submitted' currently. Maybe I'm
> overthinking all this :)
Well unless I'm mistaken, the purpose of the field for which it was originally
introduced is as I stated it, to track where we (layer maintainers) are in
sending things upstream since the expectation is that we will be the ones
doing the work required to do that. Whether or not the label(s) that get used
accurately communicate that is another matter.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-02-09 15:31 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 [this message]
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 ` [yocto] " Paul Eggleton
2012-02-08 17:37 ` Paul Eggleton
2012-02-08 17:45 ` [yocto] " Khem Raj
2012-02-08 17:45 ` Khem Raj
2012-02-08 18:04 ` Osier-mixon, Jeffrey
2012-02-08 18:45 ` [yocto] " Saul Wold
2012-02-08 18:45 ` Saul Wold
2012-02-08 21:44 ` Paul Menzel
2012-02-08 21:44 ` [OE-core] " 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=2515705.YAd3HxSNCM@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@beagleboard.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.