From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/prelink-cross: bump to version ff2561c02ade96c5d4d56ddd4e27ff064840a176
Date: Sat, 13 Jul 2024 21:53:15 +0200 [thread overview]
Message-ID: <20240713215315.77f42335@windsurf> (raw)
In-Reply-To: <CADvTj4rnf4WUO0+7n9M3WdSvV-QBpca=ivOugcr7tLL4iPvZtw@mail.gmail.com>
On Sat, 13 Jul 2024 11:47:57 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> > Peter: it means this version bump is actually fixing an issue that
> > occurs on 2024.02, so this version bump should be backported to our LTS
> > branch.
> >
> > James: this is why we ask for more explanations, so that we can figure
> > out whether a certain commit is relevant or not for our LTS branch.
>
> Do we backport build host major compiler version update fixes to LTS
> branches?
No, but when a fix is made by a bump, we need to know it to then decide
whether (or not) it should be backported to LTS branches.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-07-13 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 20:19 [Buildroot] [PATCH 1/1] package/prelink-cross: bump to version ff2561c02ade96c5d4d56ddd4e27ff064840a176 James Hilliard
2024-07-12 20:54 ` Thomas Petazzoni via buildroot
2024-07-13 12:15 ` Thomas Petazzoni via buildroot
2024-07-13 17:47 ` James Hilliard
2024-07-13 19:53 ` Thomas Petazzoni via buildroot [this message]
2024-07-14 13:24 ` Thomas Petazzoni via buildroot
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=20240713215315.77f42335@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.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