From: Nick Clifton <nickc@redhat.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>,
Mark Wielaard <mjw@redhat.com>
Subject: Should we have a 2.35.1 point release ?
Date: Tue, 15 Sep 2020 10:57:26 +0100 [thread overview]
Message-ID: <2eb8cd4e-45d6-01e0-96c3-9bf4a7098c51@redhat.com> (raw)
Hi Guys,
With all the recent fixes that have gone in to the 2.35 branch, I
was wondering whether it would be a reasonable to have a 2.35.1
point release.
What do you think ?
If we are agreed then I would probably carve it out over this weekend
(Sep 19/20).
Cheers
Nick
next reply other threads:[~2020-09-15 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 9:57 Nick Clifton [this message]
2020-09-15 10:11 ` Jose E. Marchesi
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=2eb8cd4e-45d6-01e0-96c3-9bf4a7098c51@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=mjw@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).