From: "H.J. Lu" <hjl.tools@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: 2.37 branch created.
Date: Mon, 5 Jul 2021 08:35:05 -0700 [thread overview]
Message-ID: <CAMe9rOr1W_rUaTkAuSCiUqhr7u-azz=E1oHmDmUdFLxK9gf-5w@mail.gmail.com> (raw)
In-Reply-To: <878s2na1ka.fsf@redhat.com>
On Sat, Jul 3, 2021 at 7:56 AM Nick Clifton via Binutils
<binutils@sourceware.org> wrote:
>
> Hi Everyone,
>
> The 2.37 branch has now been created:
>
> git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2.37-branch
>
> A snapshot of the sources is also available here:
>
> https://sourceware.org/pub/binutils/snapshots/binutils-2.36.90.tar.xz
>
> Please could all patches for the branch be run by me.
> The rules for the branch are:
>
> * No new features.
> * Target specific bug fixes are OK.
> * Generic bug fixes are OK if they are important and widely tested.
> * Documentation updates/fixes are OK.
> * Translation updates are OK.
> * Fixes for testsuite failures are OK.
>
> Ideally I would like to make the release happen in two weeks time,
> i.e. July 18. Which I hope will be enough time for everyone
> to get their final fixes in.
>
>
> In addition, now that this branch has been cut, we are dropping the
> requirement for ChangeLog entries to be submitted with patches to the
> mainline sources. They are not forbidden, but they are optional.
> Instead we will be generating changelogs for future releases based on
> the git commit messages. As such, please could anyone checking in a
> patch endevour to ensure that the commit messages are thorough.
>
Is it too late to fix:
https://sourceware.org/bugzilla/show_bug.cgi?id=28040
for 2.37?
--
H.J.
next prev parent reply other threads:[~2021-07-05 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 14:56 Nick Clifton
2021-07-05 15:35 ` H.J. Lu [this message]
2021-07-05 15:48 ` Nick Clifton
2021-07-06 5:50 ` Matthias Klose
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='CAMe9rOr1W_rUaTkAuSCiUqhr7u-azz=E1oHmDmUdFLxK9gf-5w@mail.gmail.com' \
--to=hjl.tools@gmail.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).