From: Nick Clifton <nickc@redhat.com>
To: Binutils <binutils@sourceware.org>
Subject: 2.41 branch approaching
Date: Mon, 19 Jun 2023 10:57:48 +0100 [thread overview]
Message-ID: <950329db-cf08-2b29-142b-3489fb070213@redhat.com> (raw)
Hi Guys,
The 2.41 release is fast approaching. My current plan is create
the branch on July 2 and then release on July 23. So if anyone
has any new features that they want to see in the 2.41 release,
now is the time to submit them for review or ping the maintainers
if they are still waiting for a response.
Cheers
Nick
next reply other threads:[~2023-06-19 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:57 Nick Clifton [this message]
2023-06-21 18:29 ` Indu Bhagat
2023-06-26 5:34 ` Matthias Klose
2023-06-28 10:58 ` Nick Clifton
2023-06-28 15:21 ` Matthias Klose
2023-06-28 15:59 ` Nick Clifton
2023-06-28 16:27 ` Matthias Klose
2023-06-29 9:34 ` Matthias Klose
2023-06-29 11:44 ` Nick Clifton
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=950329db-cf08-2b29-142b-3489fb070213@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
/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).