From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 1/3] Update bitbake from the upstream.
Date: Thu, 8 Nov 2018 12:08:47 +0300 [thread overview]
Message-ID: <6d6dd3a3-6b5c-a341-fa91-951ade31e2df@ilbers.de> (raw)
In-Reply-To: <20181107185812.12529eeb@md1za8fc.ad001.siemens.net>
On 11/7/18 8:58 PM, Henning Schild wrote:
> Am Wed, 7 Nov 2018 17:09:53 +0100
> schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
>
>> Origin: https://github.com/openembedded/bitbake.git
>> Commit: 701f76f773a6e77258f307a4f8e2ec1a8552f6f3
> Please include the complete "git show" header here, or at least the
> name of the patch. Just to be extra sure we find that again, should the
> hash change ...
Ok.
I've just taken as an example the latest bitbake update commit
(a6e101f5) in isar tree.
> This is one behind the last release and the only diff is a
> user-manual-change. I think that is ok, but why did you not go for the
> release?
The reason is that user-manual-change will not hurt.
No problem - I will switch V2 series to the release 1.40.0 commit:
commit 2820e7aab2203fc6cf7127e433a80b7d13ba75e0
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Sat Oct 20 14:26:41 2018 +0100
bitbake: Bump version to 1.40.0
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Maxim.
> Henning
>
>> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
[snip]
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2018-11-08 9:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 16:09 [PATCH 0/3] bitbake upstream update and eliminate no-gpg-check option usage Maxim Yu. Osipov
2018-11-07 16:09 ` [PATCH 1/3] Update bitbake from the upstream Maxim Yu. Osipov
2018-11-07 17:58 ` Henning Schild
2018-11-08 9:08 ` Maxim Yu. Osipov [this message]
2018-11-07 16:09 ` [PATCH 2/3] meta: Set LAYERSERIES_* variables Maxim Yu. Osipov
2018-11-07 16:20 ` Jan Kiszka
2018-11-07 16:39 ` Maxim Yu. Osipov
2018-11-07 16:41 ` Jan Kiszka
2018-11-07 17:24 ` Maxim Yu. Osipov
2018-11-07 17:26 ` Jan Kiszka
2018-11-07 16:09 ` [PATCH 3/3] isar-bootstrap: Eliminate no-gpg-check option usage Maxim Yu. Osipov
2018-11-07 17:38 ` Henning Schild
2018-11-08 7:57 ` Maxim Yu. Osipov
2018-11-12 9:30 ` Maxim Yu. Osipov
2018-11-27 9:43 ` Henning Schild
2018-11-27 10:15 ` Maxim Yu. Osipov
2018-12-03 11:49 ` Maxim Yu. Osipov
2018-12-03 12:52 ` Jan Kiszka
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=6d6dd3a3-6b5c-a341-fa91-951ade31e2df@ilbers.de \
--to=mosipov@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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