From: Darren Hart <dvhart@linux.intel.com>
To: William Mills <wmills@ti.com>
Cc: poky <poky@yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [poky] Commit and Patch message guidelines - fifth draft
Date: Thu, 12 May 2011 20:12:11 -0700 [thread overview]
Message-ID: <4DCCA18B.4040505@linux.intel.com> (raw)
In-Reply-To: <4DCC9168.1090100@ti.com>
On 05/12/2011 07:03 PM, William Mills wrote:
>
> On 05/12/2011 07:49 PM, Darren Hart wrote:
>> There is: http://www.yoctoproject.org/community/mailing-lists
>>
>> Which needs to be updated to better reflect the oe-core aspect I think.
>
> This might be at least one source of the cross posting as people are not
> sure poky vs oe-core.
>
>>> It seems to me there is a whole bunch of discussion happening on the
>>> poky list about making changes that that would effect everyone using
>>> openembedded-core. Do we have two lists for discussion of stuff that
>>> effect the oe-core?
>>
>> No. As I understand it, things that go into poky.git/meta and things
>> that go into oe-core should be sent to the openembedded-core list. Patch
>> series for poky.git should be isolated in such a way so that they do not
>> include changes to meta (oe-core) and other areas at the same time.
> >
> > Does anyone have a different view?
> >
>
> This seems logical to me. Thanks. I also think discussion of a
> potential patch should be done on the list that the patch would go to yes?
>
> Maybe we could drive that definition to ground and get the mailing list
> page updated.
>
> ---
>
> So above, perhaps my "whole bunch" was overstated. Let me retract that
> and say at least some.
>
> I don't mean to pick on you Darren;
Oh, I think I asked for this one :-)
> I really am just trying to
> understand and an example is often helpful. Earlier you and Richard
> were discussing directdisc images [1] with a suggestion that it might be
> ripe for removal. Should that have been on oe-core?
>
You are correct. I should have sent that to oe-core as the
implementation in question is in poky.git/meta (ie oe-core). Clearly,
this is easy to miss and will take some time for us to get there.
Thanks for pointing that out!
> [1] https://lists.yoctoproject.org/pipermail/poky/2011-May/006106.htm
>
> Thanks,
> Bill
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
WARNING: multiple messages have this Message-ID (diff)
From: Darren Hart <dvhart@linux.intel.com>
To: William Mills <wmills@ti.com>
Cc: poky <poky@yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Commit and Patch message guidelines - fifth draft
Date: Thu, 12 May 2011 20:12:11 -0700 [thread overview]
Message-ID: <4DCCA18B.4040505@linux.intel.com> (raw)
In-Reply-To: <4DCC9168.1090100@ti.com>
On 05/12/2011 07:03 PM, William Mills wrote:
>
> On 05/12/2011 07:49 PM, Darren Hart wrote:
>> There is: http://www.yoctoproject.org/community/mailing-lists
>>
>> Which needs to be updated to better reflect the oe-core aspect I think.
>
> This might be at least one source of the cross posting as people are not
> sure poky vs oe-core.
>
>>> It seems to me there is a whole bunch of discussion happening on the
>>> poky list about making changes that that would effect everyone using
>>> openembedded-core. Do we have two lists for discussion of stuff that
>>> effect the oe-core?
>>
>> No. As I understand it, things that go into poky.git/meta and things
>> that go into oe-core should be sent to the openembedded-core list. Patch
>> series for poky.git should be isolated in such a way so that they do not
>> include changes to meta (oe-core) and other areas at the same time.
> >
> > Does anyone have a different view?
> >
>
> This seems logical to me. Thanks. I also think discussion of a
> potential patch should be done on the list that the patch would go to yes?
>
> Maybe we could drive that definition to ground and get the mailing list
> page updated.
>
> ---
>
> So above, perhaps my "whole bunch" was overstated. Let me retract that
> and say at least some.
>
> I don't mean to pick on you Darren;
Oh, I think I asked for this one :-)
> I really am just trying to
> understand and an example is often helpful. Earlier you and Richard
> were discussing directdisc images [1] with a suggestion that it might be
> ripe for removal. Should that have been on oe-core?
>
You are correct. I should have sent that to oe-core as the
implementation in question is in poky.git/meta (ie oe-core). Clearly,
this is easy to miss and will take some time for us to get there.
Thanks for pointing that out!
> [1] https://lists.yoctoproject.org/pipermail/poky/2011-May/006106.htm
>
> Thanks,
> Bill
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-05-13 3:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 19:57 Commit and Patch message guidelines - fifth draft Mark Hatle
2011-05-12 21:00 ` [poky] " Darren Hart
2011-05-12 21:00 ` Darren Hart
2011-05-12 21:10 ` [poky] " Mark Hatle
2011-05-12 21:10 ` Mark Hatle
2011-05-12 21:11 ` [poky] " Darren Hart
2011-05-12 21:11 ` Darren Hart
2011-05-12 22:05 ` [poky] " William Mills
2011-05-12 22:05 ` William Mills
2011-05-12 23:49 ` [poky] " Darren Hart
2011-05-12 23:49 ` Darren Hart
2011-05-13 2:03 ` [poky] " William Mills
2011-05-13 2:03 ` William Mills
2011-05-13 3:12 ` Darren Hart [this message]
2011-05-13 3:12 ` Darren Hart
2011-05-15 15:03 ` [poky] " Leon Woestenberg
2011-05-15 15:03 ` Leon Woestenberg
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=4DCCA18B.4040505@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
--cc=wmills@ti.com \
/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.