From: "Aleksandar Nikolic" <aleksandar.nikolic010@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] scripts/install-buildtools: Update to 4.0.21
Date: Tue, 24 Sep 2024 05:12:31 -0700 [thread overview]
Message-ID: <15848.1727179951712740986@lists.openembedded.org> (raw)
In-Reply-To: <289C5BB3-5EEC-4C28-B85C-F4148FE5DE41@arm.com>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
On Tue, Sep 24, 2024 at 01:30 PM, Ross Burton wrote:
>
> On 24 Sep 2024, at 08:57, Aleksandar Nikolic via lists.openembedded.org
> <aleksandar.nikolic010=gmail.com@lists.openembedded.org> wrote:
>
>> I was thinking since 4.1 (and higher versions) are EOL and since this is
>> the kirkstone branch, the buildtools should also reflect the latest
>> available release on the kirkstone branch, which is 4.0.21. But I am not
>> really sure what's the right solution here, if someone else could chime
>> in, I'd be thankful.
>
> If these patches are for a stable branch then please make that obvious by
> putting [kirkstone] in the subject.
I forgot to do that and only saw it after the patches were sent out (did it correctly for scarthgap later). Should I send a new patch series (v2) with [kirkstone] in the subject?
Aleksandar
>
> Ross
[-- Attachment #2: Type: text/html, Size: 970 bytes --]
prev parent reply other threads:[~2024-09-24 12:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 8:59 [PATCH 1/4] install-buildtools: support buildtools-make-tarball and update to 4.1 Aleksandar Nikolic
2024-09-23 8:59 ` [PATCH 2/4] install-buildtools: remove md5 checksum validation Aleksandar Nikolic
2024-09-23 8:59 ` [PATCH 3/4] install-buildtools: fix "test installation" step Aleksandar Nikolic
2024-09-23 8:59 ` [PATCH 4/4] scripts/install-buildtools: Update to 4.0.21 Aleksandar Nikolic
2024-09-23 9:06 ` [OE-core] " Jose Quaresma
2024-09-24 7:57 ` Aleksandar Nikolic
2024-09-24 11:30 ` [OE-core] " Ross Burton
2024-09-24 12:12 ` Aleksandar Nikolic [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=15848.1727179951712740986@lists.openembedded.org \
--to=aleksandar.nikolic010@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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