From: Nick Clifton <nickc@redhat.com>
To: Palmer Dabbelt <palmer@dabbelt.com>, binutils@sourceware.org
Subject: Re: The 2.38 branch has been created.
Date: Tue, 8 Feb 2022 15:43:29 +0000 [thread overview]
Message-ID: <a971f667-1f63-acdd-a2ba-9ee7acaf8b89@redhat.com> (raw)
In-Reply-To: <mhng-5a3db3ad-5439-4e73-a495-30872b748258@palmer-ri-x1c9>
Hi Palmer,
> Sorry for the extremely late notice, but we just found that we'd missed the fix for this version checking issue. I've posted a patch, as Nelson pointed out in that thread
> <https://sourceware.org/pipermail/binutils/2022-February/119684.html> we're hoping it's not too late for 2.38 -- no big deal if it is, though.
Nelson has already pinged me about this. If you can get the patch in today
(Tue Feb 8) then it should be OK. I hoping to make the release tomorrow...
Cheers
Nick
next prev parent reply other threads:[~2022-02-08 15:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 12:58 Nick Clifton
2022-01-23 13:15 ` H.J. Lu
2022-01-23 13:32 ` [PATCH] Regenerate configure files with autoconf 2.69 H.J. Lu
2022-01-24 14:59 ` The 2.38 branch has been created Nick Clifton
2022-01-25 12:39 ` Matthias Klose
2022-01-25 15:37 ` Nick Clifton
2022-01-29 5:29 ` Alan Modra
2022-01-30 13:32 ` Matthias Klose
2022-01-30 13:53 ` H.J. Lu
2022-01-30 13:58 ` Matthias Klose
2022-01-30 22:48 ` Alan Modra
2022-01-25 17:22 ` Szabolcs Nagy
2022-01-27 10:18 ` Szabolcs Nagy
2022-01-30 15:02 ` H.J. Lu
2022-02-08 2:07 ` Palmer Dabbelt
2022-02-08 15:43 ` Nick Clifton [this message]
2022-02-09 9:21 ` Fangrui Song
[not found] ` <MWHPR1201MB0110C2AE8A32FAF1A45EFEE4CB2E9@MWHPR1201MB0110.namprd12.prod.outlook.com>
2022-02-09 15:50 ` Nick Clifton
2022-02-10 4:53 ` Fangrui Song
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=a971f667-1f63-acdd-a2ba-9ee7acaf8b89@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=palmer@dabbelt.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).