From: "H.J. Lu" <hjl.tools@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: The 2.38 branch has been created.
Date: Sun, 23 Jan 2022 05:15:08 -0800 [thread overview]
Message-ID: <CAMe9rOoxLzDV9Wqa+gah-M5Q-HC-qrtwVnASUA9owWJ_qYxULw@mail.gmail.com> (raw)
In-Reply-To: <87a6foudtm.fsf@redhat.com>
On Sat, Jan 22, 2022 at 4:59 AM Nick Clifton via Binutils
<binutils@sourceware.org> wrote:
>
> Hi Everyone,
>
> The 2.38 branch has now been created:
>
> git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2_38-branch
>
> A snapshot of the sources is also available here:
>
> https://sourceware.org/pub/binutils/snapshots/binutils-2.37.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. Saturday 5th Feb 2022. Which I hope will be enough time for
> everyone to get their final fixes in.
>
Hi Nick,
All configure files master and 2.38 branches are generated by a modified
autoconf with extra --runstatedir=DIR. Shouldn't they be generated by
an unmodified autoconf?
--
H.J.
next prev parent reply other threads:[~2022-01-23 13:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 12:58 Nick Clifton
2022-01-23 13:15 ` H.J. Lu [this message]
2022-01-23 13:32 ` [PATCH] Regenerate configure files with autoconf 2.69 H.J. Lu
2022-01-24 14:59 ` The 2.38 branch has been created Nick Clifton
2022-01-25 12:39 ` Matthias Klose
2022-01-25 15:37 ` Nick Clifton
2022-01-29 5:29 ` Alan Modra
2022-01-30 13:32 ` Matthias Klose
2022-01-30 13:53 ` H.J. Lu
2022-01-30 13:58 ` Matthias Klose
2022-01-30 22:48 ` Alan Modra
2022-01-25 17:22 ` Szabolcs Nagy
2022-01-27 10:18 ` Szabolcs Nagy
2022-01-30 15:02 ` H.J. Lu
2022-02-08 2:07 ` Palmer Dabbelt
2022-02-08 15:43 ` Nick Clifton
2022-02-09 9:21 ` Fangrui Song
[not found] ` <MWHPR1201MB0110C2AE8A32FAF1A45EFEE4CB2E9@MWHPR1201MB0110.namprd12.prod.outlook.com>
2022-02-09 15:50 ` Nick Clifton
2022-02-10 4:53 ` Fangrui Song
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=CAMe9rOoxLzDV9Wqa+gah-M5Q-HC-qrtwVnASUA9owWJ_qYxULw@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).