Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Smith, Elliot" <elliot.smith@intel.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] cooker: Ensure BB_CONSOLE remains correct over server resets
Date: Sat, 24 Oct 2015 12:26:05 +0100	[thread overview]
Message-ID: <1445685965.21913.58.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+1hgUg7=OhPXV=fHrXzLpSeWKZekx0BkYpu1BC8zaA1H7gG2w@mail.gmail.com>

On Mon, 2015-10-19 at 13:27 +0100, Smith, Elliot wrote:
> Thanks for clarifying.
>
> Will these patches be in 2.0? From the toaster point of view, it would
> be better if the current behaviour remained for now, even though it is
> broken.
>
> We are working on a solution which will write separate build logs from
> within Toaster itself, which will mean we can keep our log download
> working when your patches do go in.
>
> However, we may not get this finished for 2.0, and it would be good if
> we could keep the Toaster log download feature working in the
> meantime.
> 
Given the other discussion I've seen, I'm assuming it would be ok to
merge these now?

Cheers,

Richard





  reply	other threads:[~2015-10-24 11:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-11  9:22 [PATCH] cooker: Ensure BB_CONSOLE remains correct over server resets Richard Purdie
2015-10-16 15:57 ` Smith, Elliot
2015-10-16 15:59   ` Richard Purdie
2015-10-19 10:32     ` Barros Pena, Belen
2015-10-19 11:39       ` Richard Purdie
2015-10-19 12:27     ` Smith, Elliot
2015-10-24 11:26       ` Richard Purdie [this message]
2015-10-26 11:12         ` Barros Pena, Belen
2015-10-27 11:21         ` Smith, Elliot
2015-10-27 12:32           ` Smith, Elliot

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=1445685965.21913.58.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=elliot.smith@intel.com \
    /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