From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Build failure
Date: Tue, 25 Jan 2011 22:51:10 +0000 [thread overview]
Message-ID: <1295995870.27814.244.camel@rex> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504DB5BB6AE6@shsmsx502.ccr.corp.intel.com>
On Tue, 2011-01-25 at 08:00 +0800, Tian, Kevin wrote:
> PR needs to be bumped in this case, which however reminds me one confusing area
> I didn't think about before.
>
> How do we handle the class changes which are inherited by many recipes? Generally
> we need bump PRs once the output of a recipe gets changed, but it looks class file
> is usually ignored.
>
> Is there any easy way to have all recipes inheriting same class file bumping their PRs,
> or has to be done by manual check?
This is a problem and its one I'm thinking we address with the sstate
checksums being part of the stamps ultimately.
Cheers,
Richard
next prev parent reply other threads:[~2011-01-25 22:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 21:36 Build failure Gary Thomas
2011-01-24 21:52 ` Tom Zanussi
2011-01-24 23:05 ` Gary Thomas
2011-01-25 0:00 ` Tian, Kevin
2011-01-25 22:51 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-14 9:15 Andreas Müller
2012-11-14 9:30 ` Andreas Müller
[not found] <BANLkTikBm0gmNd8oQ6CN+cAEbYhWEGvWPA@mail.gmail.com>
2011-04-30 14:31 ` Build Failure Colin Minihan
2011-04-30 16:10 ` Andy Walls
2011-05-01 1:28 ` Mauro Carvalho Chehab
2011-05-01 11:50 ` Vincent McIntyre
2010-08-05 5:32 [linux-next] build failure divya
2010-08-05 16:48 ` John Fastabend
2009-02-18 22:42 Build failure jonr
2009-02-18 23:47 ` Jeremy Fitzhardinge
2009-02-19 0:50 ` jonr
2008-07-30 9:29 build failure Christoph Egger
2008-07-30 9:49 ` Keir Fraser
2008-07-30 11:01 ` Christoph Egger
2007-06-08 10:24 Build failure Steinar H. Gunderson
2007-06-08 10:47 ` Steinar H. Gunderson
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=1295995870.27814.244.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=kevin.tian@intel.com \
--cc=poky@lists.pokylinux.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.