From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>,
"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
Subject: Re: [PATCH 1/1] bitbake: backport fetch2/aws: forward env-vars used in gitlab-ci K8s
Date: Thu, 30 Nov 2023 09:45:31 +0100 [thread overview]
Message-ID: <ZWhLq7bhhmNi11qM@ilbers.de> (raw)
In-Reply-To: <4a07c292ac87d6d8f261b019a6380e804b58c90c.camel@siemens.com>
On 2023-11-30 02:48, MOESSBAUER, Felix wrote:
> > I think that we as maintainers should take care of forward-porting
> > the change
> > whenever we update bitbake. Currently, we use 2.0 due to the LTS. We
> > estimate
> > that the upstream change might become part of 2.6.1, which would mean
> > we might
> > still have 2.4, 2.6 and / or 2.8 (which is the next LTS).
>
> Hi, this sounds reasonable. Is there any documentation, where the
> backported patches are tracked?
We've thought about introducing bitbake/README.Isar, but it would still be
something that one has to actively check, which is then not much better than
e.g. git log --pretty=oneline --abbrev-commit --no-decorate bitbake:
2253ad4d bitbake: backport fetch2/aws: forward env-vars used in gitlab-ci K8s
05710647 bitbake: update to Bitbake 2.0.12
a9bbdeeb bitbake: update to Bitbake 2.0.5
2a10bbb9 utils: Ensure shell function failure in python logging is correct
01084712 bitbake-diffsigs: break on first dependent task difference
a5bbc86f bitbake-diffsigs: make finding of changed signatures more robust
3c99609b bitbake: Update to 1.50.5 release
c9252baf bitbake: Update to 1.50.4 release
522ac8f8 bitbake: Update to 1.46.2 release
c2aae245 bitbake: update to version 1.44.0
ce34a501 bitbake: Update to fixed master revision
1fb4c991 bitbake: Update to the release 1.40.0
a6e101f5 Update bitbake from the upstream.
3a0254fc bitbake: Update to 1.31.2+g80f377e
ff22b2b1 Add bitbake master 7c849be
The better alternative would be a testcase.
With kind regards,
Baurzhan
next prev parent reply other threads:[~2023-11-30 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 7:50 Felix Moessbauer
2023-11-24 13:52 ` Uladzimir Bely
2023-11-24 14:00 ` Baurzhan Ismagulov
2023-11-25 8:19 ` Jan Kiszka
2023-11-29 10:11 ` Baurzhan Ismagulov
2023-11-30 2:48 ` MOESSBAUER, Felix
2023-11-30 8:45 ` Baurzhan Ismagulov [this message]
2023-11-29 9:24 ` Uladzimir Bely
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=ZWhLq7bhhmNi11qM@ilbers.de \
--to=ibr@radix50.net \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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