From: Patrick Ohly <patrick.ohly@intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] meta/conf/layer.conf: Add recommended download layer
Date: Thu, 24 Nov 2016 12:13:40 +0100 [thread overview]
Message-ID: <1479986020.6873.36.camel@intel.com> (raw)
In-Reply-To: <f2e7d5d6-7094-10b6-16bc-9398c8bb828e@windriver.com>
On Wed, 2016-11-23 at 13:42 -0600, Mark Hatle wrote:
> On 11/23/16 12:56 PM, Martin Jansa wrote:
> > "Have all patches applied to BitBake and OpenEmbedded-Core (if present)
> > been submitted to the open source community?"
> >
> > Shouldn't the wording be change to something like "all applicable
> > patches" or "all generally useful patches"?
> >
> > It seems strange to send project specific patches together with cover
> > saying that they aren't generally applicable and shouldn't be merged,
> > just because of this requirement.
>
> It was done this way to prevent people from cheating and claiming something was
> (effectively) not useful/applicable/etc when it some special secret sauce.
Perhaps one could use [FYI] instead of [PATCH] in the mail subject to
make the intention even clearer, and patchwork could get configured to
not track such patches or at least not show them as new? Just a thought.
As it stands now, there's an entry for this patch that someone
(Richard?) will have to close:
https://patchwork.openembedded.org/series/4056/
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2016-11-24 11:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 17:42 [PATCH] Add recommended layer to oe-core Mark Hatle
2016-11-23 17:42 ` [PATCH] meta/conf/layer.conf: Add recommended download layer Mark Hatle
2016-11-23 18:10 ` Martin Jansa
2016-11-23 18:38 ` Mark Hatle
2016-11-23 18:56 ` Martin Jansa
2016-11-23 19:42 ` Mark Hatle
2016-11-24 1:16 ` Christopher Larson
2016-11-24 3:00 ` Mark Hatle
2016-11-24 11:13 ` Patrick Ohly [this message]
2016-11-24 14:03 ` Philip Balister
2016-11-24 16:14 ` Burton, Ross
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=1479986020.6873.36.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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