From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] local.conf.sample: Cleanup and improve
Date: Fri, 12 Aug 2011 10:09:25 -0500 [thread overview]
Message-ID: <4E454225.40603@windriver.com> (raw)
In-Reply-To: <1313159714.6733.157.camel@phil-desktop>
On 8/12/11 9:35 AM, Phil Blundell wrote:
> On Fri, 2011-08-12 at 15:33 +0100, Richard Purdie wrote:
>>> Should patch resolution be noop by default? (I suspect due to my above concern
>>> w/ ipkg, changing the behavior now is likely a bad idea.)
>>
>> Good question. I suspect most people prefer noop and it would make more
>> sense for unattended builds...
>
> Agreed, I think noop is probably the best/least surprising default
> behaviour.
My suggestion then is a separate commit that sets noop as the default behavior..
(I almost always run w/ noop set.)
--Mark
> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2011-08-12 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 12:49 [PATCH] local.conf.sample: Cleanup and improve Richard Purdie
2011-08-12 13:49 ` Mark Hatle
2011-08-12 14:33 ` Richard Purdie
2011-08-12 14:35 ` Phil Blundell
2011-08-12 15:09 ` Mark Hatle [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=4E454225.40603@windriver.com \
--to=mark.hatle@windriver.com \
--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