From: Scott Garman <scott.a.garman@intel.com>
To: yocto@yoctoproject.org
Subject: Re: [for denzil] kernel.bbclass: Copy bounds.h only if it exists, needed for 2.6.x.
Date: Wed, 01 Aug 2012 09:46:30 -0700 [thread overview]
Message-ID: <50195D66.2020503@intel.com> (raw)
In-Reply-To: <CAMvUbCwZEiOQU=r5YYLtbbn7V1acgyYNN1i8ySJgRSSVSp8+mA@mail.gmail.com>
On 08/01/2012 02:08 AM, Leon Woestenberg wrote:
> Hello Koen,
>
> On 08/01/2012 08:55 AM, Koen Kooi wrote:
>> Shouldn't this be sent to the oe-core list?!?!?
>>
> It was intended for the denzil branch ([for denzil]) of Yocto, that's
> why I sent it to yocto@yoctoproject.org.
>
> If that was wrong reasoning, let me know, I would be glad to change
> workflow if I know why.
Hi Leon,
Since Yocto is built upon oe-core, changes to files that live in oe-core
should really be sent to the oe-core ML. Our workflow is then to pick
things up from oe-core and move them into the poky git repository.
Both oe-core and poky have denzil branches this patch applies to, so
you'd still make mention in your subject line that the patch is intended
for denzil.
The main reason to submit patches to the Yocto ML is if it's specific to
the meta-yocto layer you find in the Poky git repository, or to discuss
overall Yocto issues.
Just some things to keep in mind for the future.
Thanks,
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
prev parent reply other threads:[~2012-08-01 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 20:35 [for denzil] kernel.bbclass: Copy bounds.h only if it exists, needed for 2.6.x sidebranch.openembedded
2012-07-31 22:00 ` Scott Garman
2012-07-31 22:08 ` Leon Woestenberg
2012-08-01 6:55 ` Koen Kooi
2012-08-01 9:08 ` Leon Woestenberg
2012-08-01 16:46 ` Scott Garman [this message]
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=50195D66.2020503@intel.com \
--to=scott.a.garman@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.