From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] local.conf.sample: add PATH to SSTATE_MIRRORS comments
Date: Fri, 12 Oct 2012 20:22:56 +0200 [thread overview]
Message-ID: <50786000.7010008@linaro.org> (raw)
In-Reply-To: <50785C63.5060303@linux.intel.com>
W dniu 12.10.2012 20:07, Saul Wold pisze:
> On 10/11/2012 06:27 AM, Paul Eggleton wrote:
>> meta/conf/local.conf.sample | 7 +++++--
>> 1 file changed, 5 insertions(+), 2 deletions(-)
> I think this is really a Poky File, so should go to the
> poky@yoctoproject.org!
For me this file is part of OE-Core so list is proper. If OE-Core has
some Poky files then maybe consider moving them to separate layer?
Look at OE-Core from perspective of external developers. They change
files and then send patches here. Would you say them "go to other ML
with it" just because of history relations when they did proper thing?
next prev parent reply other threads:[~2012-10-12 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 13:27 [PATCH] local.conf.sample: add PATH to SSTATE_MIRRORS comments Paul Eggleton
2012-10-12 18:07 ` Saul Wold
2012-10-12 18:20 ` Paul Eggleton
2012-10-12 18:22 ` Marcin Juszkiewicz [this message]
2012-10-15 5:34 ` Anders Darander
2012-10-15 8:45 ` Paul Eggleton
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=50786000.7010008@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--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