From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
poky@yoctoproject.org
Subject: Re: [PATCH] maintainers.inc: add missing recipes
Date: Wed, 15 Jun 2016 11:10:44 +0100 [thread overview]
Message-ID: <1465985444.13979.221.camel@linuxfoundation.org> (raw)
In-Reply-To: <1465465884-26334-1-git-send-email-alexander.kanavin@linux.intel.com>
On Thu, 2016-06-09 at 12:51 +0300, Alexander Kanavin wrote:
> Most of the additions are these:
> 1) Missing variants for a recipe (-native, -cross, etc.)
> 2) Recently added recipes; the maintainer is typically the person
> who submitted the addition
>
> If you disagree with the assignments, speak up!
I'm a little concerned with this patch. We should only be adding native
or nativesdk recipes which are native or nativesdk only. We don't have
very many of those. In the other cases, we should be able to infer the
same maintainer from the target version. Could you have a quick look
over these entries and see if we should be inferring some of them
suggesting a problem in that inferring code, wherever it may be. I just
worry we'd end up adding all -native and nativesdk- variants to this
file which seems a bit pointless...
Cheers,
Richard
next prev parent reply other threads:[~2016-06-15 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 9:51 [PATCH] maintainers.inc: add missing recipes Alexander Kanavin
2016-06-15 10:10 ` Richard Purdie [this message]
2016-06-15 12:18 ` Alexander Kanavin
-- strict thread matches above, loose matches on Subject: below --
2016-08-26 15:35 Alexander Kanavin
2016-09-12 11:50 Alexander Kanavin
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=1465985444.13979.221.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--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 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.