public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: binutils@sourceware.org, Nick Clifton <nickc@redhat.com>
Subject: Re: The 2.38 branch has been created.
Date: Mon, 07 Feb 2022 18:07:09 -0800 (PST)	[thread overview]
Message-ID: <mhng-5a3db3ad-5439-4e73-a495-30872b748258@palmer-ri-x1c9> (raw)
In-Reply-To: <87a6foudtm.fsf@redhat.com>

On Sat, 22 Jan 2022 04:58:45 PST (-0800), 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.

Sorry for the extremely late notice, but we just found that we'd missed 
the fix for this version checking issue.  I've posted a patch, as Nelson 
pointed out in that thread 
<https://sourceware.org/pipermail/binutils/2022-February/119684.html> 
we're hoping it's not too late for 2.38 -- no big deal if it is, though.

Thanks!

  parent reply	other threads:[~2022-02-08  2:07 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
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 [this message]
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=mhng-5a3db3ad-5439-4e73-a495-30872b748258@palmer-ri-x1c9 \
    --to=palmer@dabbelt.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).