From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 0/2] Fix parse errors
Date: Tue, 28 Jun 2011 10:16:53 -0700 [thread overview]
Message-ID: <4E0A0C85.80103@mentor.com> (raw)
In-Reply-To: <BANLkTikUF5FUaoyWDzJ61dnj7JmNo876eA@mail.gmail.com>
On 06/28/2011 09:54 AM, Otavio Salvador wrote:
> On Tue, Jun 28, 2011 at 13:49, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>> Can you describe a use case?
>>
>> Rolling out a fix for the generic package without having to rebuild it N
>> times.
>
> When doing this fix you should bump PR, right? in this case, this will
> be (or ought to be) rebuild for all machines thus for me seems it will
> be the same end result.
It will be, yes. What Koen is saying is that if you're a feed using
distribution you don't NEED to kick off the build for N machines, just N
architectures (since you can use sysvinit-getty-r2 and sysvinit-r3 just
fine, if there weren't any changes to the getty subpackage).
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-06-28 17:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 14:40 [meta-oe][PATCH 0/2] Fix parse errors Otavio Salvador
2011-06-28 14:40 ` [meta-oe][PATCH 1/2] systemd: set all packages PACKAGE_ARCH to MACHINE_ARCH Otavio Salvador
2011-06-28 14:40 ` [meta-oe][PATCH 2/2] task-x11: " Otavio Salvador
2011-06-28 14:51 ` [meta-oe][PATCH 0/2] Fix parse errors Koen Kooi
2011-06-28 14:59 ` Otavio Salvador
2011-06-28 15:35 ` Koen Kooi
2011-06-28 16:25 ` Otavio Salvador
2011-06-28 16:49 ` Koen Kooi
2011-06-28 16:54 ` Otavio Salvador
2011-06-28 17:16 ` Tom Rini [this message]
2011-06-28 17:46 ` Otavio Salvador
2011-06-28 17:14 ` Frans Meulenbroeks
2011-06-28 17:20 ` Tom Rini
2011-06-28 17:55 ` Frans Meulenbroeks
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=4E0A0C85.80103@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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 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.