From: Jan Beulich <jbeulich@suse.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: 2.43.1 release this weekend
Date: Mon, 12 Aug 2024 10:43:10 +0200 [thread overview]
Message-ID: <72c1c3fb-8400-4ed9-a051-f57efe2996ee@suse.com> (raw)
In-Reply-To: <00a1c7a6-a878-4709-b4b6-194b9a3d8b0d@redhat.com>
On 12.08.2024 10:38, Nick Clifton wrote:
> I am going to create a point release update or the 2.43 release
> this weekend.
>
> Several important bug fixes have gone into the branch recently,
> including one that could affect any target (PR 31956), so I think
> that the release is warranted.
>
> Thus if you have any other bug fixes which you would like to see
> in 2,43,1, (and which have already been approved for the mainline)
> now is the time to commit them to the branch.
I'm still working on one (maybe two, yet to verify) regressions on x86.
Jan
next prev parent reply other threads:[~2024-08-12 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 8:38 Nick Clifton
2024-08-12 8:43 ` Jan Beulich [this message]
2024-08-12 15:48 ` Nick Clifton
2024-08-12 15:51 ` Jan Beulich
2024-08-14 9:37 ` Jan Beulich
2024-08-12 8:46 ` Sam James
2024-08-14 13:39 ` H.J. Lu
2024-08-15 23:21 ` H.J. Lu
2024-08-16 13:57 ` Nick Clifton
2024-08-16 13:58 ` H.J. Lu
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=72c1c3fb-8400-4ed9-a051-f57efe2996ee@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).