All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Cc: Koen Kooi <koen@beagleboard.org>
Subject: Re: Upstream-Status finally @ 100%
Date: Thu, 09 Feb 2012 12:30:34 +0000	[thread overview]
Message-ID: <1636213.TrTs1YKXOm@helios> (raw)
In-Reply-To: <F3D9189D-F27C-4C90-AD58-5071F83FA2AF@beagleboard.org>

On Thursday 09 February 2012 13:22:10 Koen Kooi wrote:
> I find the 'pending' confusing, is it 'pending submission' or 'pending
> approval'? I'm marking patches in meta-oe with 'Upstream-status: Unknown'
> as default instead of 'Pending' to make it a bit clearer. And patches
> marked 'inappropriate' won't go in, it's 'rejected', 'unknown' or 'needs
> work' in those cases. I'm not going to guess what upstream might think of
> it, since I can't speak for them.

I think the distinction between Pending and Unknown is important. The status 
is not completely unknown - the person who set it made an assessment that the 
patch should be appropriate for sending upstream, even if it would need 
further cleanup beforehand. Maybe "Pending" isn't the best word, I'm not sure, 
but "Unknown" is not right either.

> All patches in OE-core now have an Upstream-status, but how many have an
> *incorrect* Upstream-status?

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 what matters - it's a tool 
you can use in the separate exercise of going through the patches we do have 
and trying to get them merged upstream.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2012-02-09 12:30 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 [this message]
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     ` [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=1636213.TrTs1YKXOm@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.