All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: "Björn Stenberg" <bjst@enea.com>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>
Subject: Re: Upstream-Status finally @ 100%
Date: Wed, 08 Feb 2012 10:57:25 -0800	[thread overview]
Message-ID: <4F32C595.4040508@linux.intel.com> (raw)
In-Reply-To: <20120208100718.GB8335@giant>

On 02/08/2012 02:07 AM, Björn Stenberg wrote:
> Saul Wold wrote:
>> After getting some final patches yesterday, we made it to 100% with
>> patch Upsteam-Status.
>
> Who sets the Upstream-Status? Are there guidelines how to do it?
>
The developer of the patch submitted to any OE branch (oe-core, meta-oe, 
...) should add the appropriate Upstream-Status entry.

See: http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

We had a big push within the OE-Core team to try and determine if 
patches are appropriate for upstream or not.

> I spoke to the author of curl and mentioned the two patches in Yocto against it, both of which are marked as "Upstream-Status: Inappropriate". He said those patches were never submitted to him.
>
> Are we dismissing patches without even giving upstream a chance to comment?

In some cases yes we might be doing that, particularly patches that 
seemed to be specific to the OE cross compilation environment or to deal 
with packaging with in the embedded space where marked as Inappropriate. 
  Once we get though round one of the obvious potential upstream-able 
patches we can revisit other.

If the author of curl would like to review and/or implement modification 
for OE that would be awesome, feel free to share the patches with them.

Sau!



  reply	other threads:[~2012-02-08 18:57 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 [this message]
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=4F32C595.4040508@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=bjst@enea.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.