From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] sstatesig.py: Move package exclusion list to the layer config
Date: Fri, 24 Feb 2012 00:15:21 +0000 [thread overview]
Message-ID: <1330042521.25226.4.camel@ted> (raw)
In-Reply-To: <CAP9ODKomVXg1Ry=o3ao_yWdiOQK6f2ViG86xHgmsrfML9BvkHg@mail.gmail.com>
On Thu, 2012-02-23 at 08:46 -0200, Otavio Salvador wrote:
> On Thu, Feb 23, 2012 at 08:17, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > +SIGGEN_EXCLUDERECIPES_ABISAFE = "sysvinit-inittab shadow-securetty opkg-config-base netbase formfactor xserver-xf86-config pointercal base-files"
>
> I would prefer one package per line here so it is easier to read a
> diff changing this, in future.
I'd meant to change this but when it came around to dealing with the
patches, I forgot, sorry :(.
We can change it as a subsequent patch...
Cheers,
Richard
prev parent reply other threads:[~2012-02-24 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 10:17 [PATCH] sstatesig.py: Move package exclusion list to the layer config Richard Purdie
2012-02-23 10:46 ` Otavio Salvador
2012-02-24 0:15 ` Richard Purdie [this message]
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=1330042521.25226.4.camel@ted \
--to=richard.purdie@linuxfoundation.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