From: Nick Clifton <nickc@redhat.com>
To: binutils@sourceware.org
Subject: The 2.38 branch is open for normal commits
Date: Wed, 09 Feb 2022 13:39:34 +0000 [thread overview]
Message-ID: <87ee4c17mx.fsf@redhat.com> (raw)
Hi Guys,
The 2.38 release is now out, so the 2.38 branch is open for commits as
normal. Ie, there is no longer a need for all commits to be run past
me. Any maintainer can provide approval.
As usual however please be aware that point releases from the 2.38
branch are only likely to be made if an important bug has been fixed.
(Or more likely, several important bugs have been fixed...)
Point releases are not made for new features, so it is best to just
use the mainline branch for new work.
Cheers
Nick
reply other threads:[~2022-02-09 13:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87ee4c17mx.fsf@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).