From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Alexis Lothoré" <alexis.lothore@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 12:37:43 +0200 [thread overview]
Message-ID: <20250418123743.51192de0@windsurf> (raw)
In-Reply-To: <D97IPBMKJNQL.1EF4TZDMMBRCA@bootlin.com>
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.
Best regards,
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:[~2025-04-18 10:37 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 [this message]
2025-04-18 18:28 ` Alexis Lothoré 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=20250418123743.51192de0@windsurf \
--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