From: Patrick Steinhardt <ps@pks.im>
To: Mike Lothian <mike@fireburn.co.uk>
Cc: git@vger.kernel.org
Subject: Re: Build failure on RHEL7 with 2.47.0
Date: Tue, 22 Oct 2024 15:55:56 +0200 [thread overview]
Message-ID: <Zxeu7GbcXa-kOzLf@pks.im> (raw)
In-Reply-To: <CAHbf0-GMV9VS7BAjvZiNENNOdZqV3jQ4+0k1kTZLkQhFT=6D-Q@mail.gmail.com>
On Tue, Oct 22, 2024 at 02:04:52PM +0100, Mike Lothian wrote:
> Have I done something silly or is it just too old?
No, you haven't done anything silly. These are all getting fixed by the
patch series posted at [1]. I'd be happy to hear whether those patches
fix the issue for you.
Patrick
[1]: https://lore.kernel.org/git/cover.1729506329.git.ps@pks.im/
next prev parent reply other threads:[~2024-10-22 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 13:04 Build failure on RHEL7 with 2.47.0 Mike Lothian
2024-10-22 13:55 ` Patrick Steinhardt [this message]
2024-10-22 14:03 ` Torsten Bögershausen
2024-10-22 21:30 ` brian m. carlson
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=Zxeu7GbcXa-kOzLf@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=mike@fireburn.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).