From: Jan Beulich <jbeulich@suse.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: 2.41 branch created
Date: Fri, 28 Jul 2023 07:51:55 +0200 [thread overview]
Message-ID: <9386df7e-f348-836a-72ca-8ef0a6a130fb@suse.com> (raw)
In-Reply-To: <87cz19tfh1.fsf@redhat.com>
Nick,
On 03.07.2023 13:13, Nick Clifton via Binutils wrote:
> Hi Everyone,
>
> The 2.41 branch has now been created:
>
> git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2_41-branch
>
> A snapshot of the sources is also available here:
>
> https://sourceware.org/pub/binutils/snapshots/binutils-2.40.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. 23 July. Which I hope will be enough time for everyone
> to get their final fixes in.
with the MIPS things out of the way, I wonder if you would want to
further wait for the regression fix for PR gas/30688. The code
change as shown in the bug looks fine testing-wise, but I'm
struggling a little with the testsuite additions (targets once
again behave too differently in certain aspects). I expect to have
this sorted (and a final test run done) later in the day.
Jan
next prev parent reply other threads:[~2023-07-28 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 11:13 Nick Clifton
2023-07-21 10:05 ` Maciej W. Rozycki
2023-07-21 15:47 ` Nick Clifton
2023-07-28 5:18 ` Maciej W. Rozycki
2023-07-28 5:51 ` Jan Beulich [this message]
2023-07-28 8:54 ` Nick Clifton
2023-07-30 0:55 ` 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=9386df7e-f348-836a-72ca-8ef0a6a130fb@suse.com \
--to=jbeulich@suse.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).