From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: Request for bitbake update
Date: Fri, 28 Sep 2018 09:02:05 +0200 [thread overview]
Message-ID: <4bf240cd-cd1b-e60f-a113-93d8c27023ed@siemens.com> (raw)
In-Reply-To: <eeb4dd8c-7940-ba39-15b7-a64482d35af4@ilbers.de>
On 28.09.18 08:59, Maxim Yu. Osipov wrote:
> Hi Jan,
>
> Should we include this into the current isar release?
> Or we may postpone after release?
There is a risk that changes along the update cause troubles, and those should
be identified first. If you want to release today, it's likely too late for this
step.
Jan
>
> Kind regards,
> Maxim.
>
> On 9/7/18 12:55 PM, Jan Kiszka wrote:
>> Hi all,
>>
>> can we move to some bitbake >= 0594faa0b52ce5dbd948d836d88617d38d9862d1? It
>> fixes the log display when bitbake fails during early startup, specifically
>> when the output is redirected (kas, CI systems,...).
>>
>> TIA,
>> Jan
>>
>
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2018-09-28 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 9:55 Jan Kiszka
2018-09-28 6:59 ` Maxim Yu. Osipov
2018-09-28 7:02 ` Jan Kiszka [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=4bf240cd-cd1b-e60f-a113-93d8c27023ed@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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