From: William Mills <wmills@ti.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: poky <poky@yoctoproject.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.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 18:05:43 -0400 [thread overview]
Message-ID: <4DCC59B7.1070309@ti.com> (raw)
In-Reply-To: <4DCC4D17.7000600@linux.intel.com>
On 05/12/2011 05:11 PM, Darren Hart wrote:
> One more thing. There is a great deal of cross-posting to the various
> lists. We should discourage this. At least mentioning somewhere in here
> that patches should be sent to the appropriate list with maintainers and
> involved developers on CC and not cross posted would be a help.
Ok, so I am going to go ahead and ask the dumb question. Where is the
write up that say what list is for what?
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?
-- Bill
next prev parent reply other threads:[~2011-05-12 22:19 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 [this message]
2011-05-12 23:49 ` Darren Hart
2011-05-13 2:03 ` William Mills
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=4DCC59B7.1070309@ti.com \
--to=wmills@ti.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@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