From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Mike Lothian <mike@fireburn.co.uk>, git@vger.kernel.org
Subject: Re: Build failure on RHEL7 with 2.47.0
Date: Tue, 22 Oct 2024 21:30:19 +0000 [thread overview]
Message-ID: <ZxgZa74fplSUUL5W@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <20241022140340.GA31399@tb-raspi4>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On 2024-10-22 at 14:03:40, Torsten Bögershausen wrote:
> On Tue, Oct 22, 2024 at 02:04:52PM +0100, Mike Lothian wrote:
> > Hi
> >
> > I'm seeing build failures on RHEL7 when trying to build 2.47.0 - RHEL8
> > seems to be fine
> >
> >
> []
> >
> > Have I done something silly or is it just too old?
>
> 2 questions, 2 answers: No, yes.
> There hasn't been much focus on supporting these/this old platform(s)
> the last weeks or months.
> Thanks for reporting, I myself can no longer compile Git under centos 7
> any more, but I am happy to work on patches.
I think RHEL/CentOS 7 is too old to support according to our platform
support policy. It's no longer receiving regular LTS support.
The clar patches I do believe will be coming in soon, but I think users
will need to upgrade on CentOS 7 nonetheless.
--
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2024-10-22 21:30 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
2024-10-22 14:03 ` Torsten Bögershausen
2024-10-22 21:30 ` brian m. carlson [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=ZxgZa74fplSUUL5W@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=mike@fireburn.co.uk \
--cc=tboegi@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.