From: Christopher Larson <kergoth@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Problems with rebuilds caused by sstate cache changes
Date: Fri, 6 Apr 2012 11:52:25 -0700 [thread overview]
Message-ID: <130E6E43FAB0417FBB8B0CB0AACEB9A2@gmail.com> (raw)
In-Reply-To: <CAP9ODKoy9qiWiTYT7=Jz2huPRwvYJjmLs+R27GkFJj6pM7bXrQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
See the thread "Re-execution of tasks - test report and results" for further information.
--
Christopher Larson
On Friday, April 6, 2012 at 11:49 AM, Otavio Salvador wrote:
> On Fri, Apr 6, 2012 at 15:48, Christopher Larson <kergoth@gmail.com (mailto:kergoth@gmail.com)> wrote:
> > Have you seen the other threads on the subject? Further, I don't think
> > rm_work is an ideal fix, considering its problematic interactions with
> > sstate in the past, unless those have been fixed?
> >
>
>
> I didn't see. The right fix would be the PRServer but from my last
> test it seems not ready for use yet. I had some wierd failures with
> git based recipes.
>
> --
> Otavio Salvador O.S. Systems
> E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
> Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org (mailto:Openembedded-core@lists.openembedded.org)
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
[-- Attachment #2: Type: text/html, Size: 2241 bytes --]
prev parent reply other threads:[~2012-04-06 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 18:45 Problems with rebuilds caused by sstate cache changes Otavio Salvador
2012-04-06 18:48 ` Christopher Larson
2012-04-06 18:49 ` Otavio Salvador
2012-04-06 18:52 ` Christopher Larson [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=130E6E43FAB0417FBB8B0CB0AACEB9A2@gmail.com \
--to=kergoth@gmail.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