From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH 1/1] bitbake: backport fetch2/aws: forward env-vars used in gitlab-ci K8s
Date: Wed, 29 Nov 2023 11:11:07 +0100 [thread overview]
Message-ID: <ZWcOO9Q5ES23XYm2@ilbers.de> (raw)
In-Reply-To: <3417bbce-a07d-4280-afa3-cd5d9f825b88@siemens.com>
On 2023-11-25 16:19, 'Jan Kiszka' via isar-users wrote:
> As discussed with Felix already in person: The only issue would be if we
> decided to update once more in the current stable series. Then there is
> the risk that we forget about this patch and overwrite it because
> upstream stable will not see it (it's a feature, not a fix). Or is 2.0.x
> EOL anyway?
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).
With kind regards,
Baurzhan
next prev parent reply other threads:[~2023-11-29 10:11 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 [this message]
2023-11-30 2:48 ` MOESSBAUER, Felix
2023-11-30 8:45 ` Baurzhan Ismagulov
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=ZWcOO9Q5ES23XYm2@ilbers.de \
--to=ibr@radix50.net \
--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