From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Cc: "Julien Olivain" <ju.o@free.fr>, <buildroot@buildroot.org>,
"Francis Laniel" <flaniel@linux.microsoft.com>,
"Thomas Perale" <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH] package/pahole: bump to version 1.28
Date: Fri, 18 Apr 2025 20:28:49 +0200 [thread overview]
Message-ID: <D99Z7C7QHM5F.OINX99GI7LWN@bootlin.com> (raw)
In-Reply-To: <20250418123743.51192de0@windsurf>
Hi Thomas,
On Fri Apr 18, 2025 at 12:37 PM CEST, Thomas Petazzoni via buildroot wrote:
> On Tue, 15 Apr 2025 23:07:39 +0200
> Alexis Lothoré <alexis.lothore@bootlin.com> wrote:
>
>> In case it has slipped through: as the issue also exists on the current
>> release branch, do you want me to send a patch targeting the 2025.02.x
>> branch to backport the upstream patch fixing the issue ? (because I guess
>> bumping the package version on the release branch is not an option ?)
>
> In fact ideally in this situation my personal preference is that from
> the start the thing gets submitted as two patches:
>
> 1. One doing the backport of the fix, without bumping the version
>
> 2. One doing the version bump, dropping the fix backport along the way
>
> This way, we can easily backport (1) to our current LTS/stable branch.
ACK, noted for next time.
Alexis
--
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-04-18 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 7:19 [Buildroot] [PATCH] package/pahole: bump to version 1.28 Alexis Lothoré via buildroot
2025-04-15 17:23 ` Julien Olivain
2025-04-15 21:07 ` Alexis Lothoré via buildroot
2025-04-18 10:37 ` Thomas Petazzoni via buildroot
2025-04-18 18:28 ` Alexis Lothoré via buildroot [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=D99Z7C7QHM5F.OINX99GI7LWN@bootlin.com \
--to=buildroot@buildroot.org \
--cc=alexis.lothore@bootlin.com \
--cc=flaniel@linux.microsoft.com \
--cc=ju.o@free.fr \
--cc=thomas.perale@mind.be \
--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