From: mengqinggang <mengqinggang@loongson.cn>
To: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: 2.42 branch has been created
Date: Wed, 24 Jan 2024 17:29:28 +0800 [thread overview]
Message-ID: <479553f9-28a4-cde4-46e1-c806ad992532@loongson.cn> (raw)
In-Reply-To: <87v87u39bb.fsf@redhat.com>
在 2024/1/15 下午11:28, Nick Clifton 写道:
> Hi Everyone,
>
> The <NEW_VERSION> branch has now been created:
>
> git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2_42-branch
>
> A snapshot of the sources is also available here:
>
> https://sourceware.org/pub/binutils/snapshots/binutils-2.41.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.
On LoongArch, I'd like to ask for your okay to cherry-pick
601c741d5ce6 LoongArch: gas: Start a new frag after instructions
that can be relaxed
27a750dd896c LoongArch: gas: Don't define LoongArch .align
32ee2b4b71c7 LoongArch: Do not emit R_LARCH_RELAX for two
register macros
Thanks
> * 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. Monday Jan 29. Which I hope will be enough time for everyone
> to get their final fixes in.
>
> Cheers
> Nick
>
next prev parent reply other threads:[~2024-01-24 9:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 15:28 Nick Clifton
2024-01-15 15:36 ` H.J. Lu
2024-01-15 15:58 ` Nick Clifton
2024-01-17 11:12 ` Xi Ruoyao
2024-01-17 11:41 ` Nick Clifton
2024-01-17 11:42 ` Xi Ruoyao
2024-01-18 11:58 ` mengqinggang
2024-01-19 10:39 ` Jan Beulich
2024-01-19 11:13 ` Nick Clifton
2024-01-24 9:29 ` mengqinggang [this message]
2024-01-24 9:42 ` Xi Ruoyao
2024-01-24 17:41 ` Nick Clifton
2024-01-25 1:40 ` mengqinggang
2024-01-24 17:40 ` Nick Clifton
2024-01-27 7:47 ` Indu Bhagat
2024-01-29 14:47 ` Nick Clifton
2024-01-30 5:37 ` Xi Ruoyao
2024-01-30 12:38 ` 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=479553f9-28a4-cde4-46e1-c806ad992532@loongson.cn \
--to=mengqinggang@loongson.cn \
--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).