All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Merging problems
Date: Sun, 21 Dec 2014 13:56:55 +0000	[thread overview]
Message-ID: <1419170215.13316.57.camel@linuxfoundation.org> (raw)
In-Reply-To: <1419165346.13316.55.camel@linuxfoundation.org>

I thought we were over the hump and I merged the series. Next autobuild
went rather red due to sstate cache usage. Reproducer was:

bitbake kernel-devsrc -c cleansstate
bitbake virtual/kernel
bitbake virtual/kernel -c clean
bitbake kernel-devsrc -c install

I've pushed yet another patch and restarted the build.

Cheers,

Richard






  reply	other threads:[~2014-12-21 13:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19 10:28 Merging problems Richard Purdie
2014-12-19 12:41 ` Richard Purdie
2014-12-19 13:07   ` Bruce Ashfield
2014-12-19 13:14     ` Bruce Ashfield
2014-12-19 13:15     ` Richard Purdie
2014-12-19 13:58       ` Bruce Ashfield
2014-12-20 11:15       ` Richard Purdie
2014-12-20 15:13         ` Bruce Ashfield
2014-12-20 22:17           ` Richard Purdie
2014-12-20 22:40           ` Richard Purdie
2014-12-21  2:04             ` Bruce Ashfield
2014-12-21 11:27               ` Richard Purdie
2014-12-21 12:35                 ` Richard Purdie
2014-12-21 13:56                   ` Richard Purdie [this message]
2014-12-22  3:40                   ` Bruce Ashfield
2014-12-22  3:38                 ` Bruce Ashfield
2014-12-20 19:19         ` Otavio Salvador
2014-12-20 22:14           ` Richard Purdie
2014-12-22 16:50         ` Martin Jansa
2014-12-22 17:00           ` Richard Purdie

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=1419170215.13316.57.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@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 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.