Openembedded Core Discussions
 help / color / mirror / Atom feed
From: William Mills <wmills@ti.com>
To: Darren Hart <dvhart@linux.intel.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 22:03:20 -0400	[thread overview]
Message-ID: <4DCC9168.1090100@ti.com> (raw)
In-Reply-To: <4DCC721D.8000705@linux.intel.com>


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; 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?

[1] https://lists.yoctoproject.org/pipermail/poky/2011-May/006106.htm

Thanks,
Bill



  reply	other threads:[~2011-05-13  2:10 UTC|newest]

Thread overview: 9+ 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:10   ` Mark Hatle
2011-05-12 21:11   ` Darren Hart
2011-05-12 22:05     ` William Mills
2011-05-12 23:49       ` Darren Hart
2011-05-13  2:03         ` William Mills [this message]
2011-05-13  3:12           ` Darren Hart
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=4DCC9168.1090100@ti.com \
    --to=wmills@ti.com \
    --cc=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox