public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: binutils@sourceware.org
Subject: The 2.40 branch has been created
Date: Sat, 31 Dec 2022 13:00:57 +0000	[thread overview]
Message-ID: <87mt739186.fsf@redhat.com> (raw)

Hi Everyone, 

  The 2.40 branch has now been created:

     git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2_40-branch

  A snapshot of the sources is also available here:

    https://sourceware.org/pub/binutils/snapshots/binutils-2.39.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. Jan 14, 2023.  Which I hope will be enough time for everyone
  to get their final fixes in.

Cheers
  Nick
  


             reply	other threads:[~2022-12-31 13:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31 13:00 Nick Clifton [this message]
2023-01-02 11:41 ` Matthias Klose
2023-01-02 11:56   ` Matthias Klose
2023-01-02 12:03   ` Andreas Schwab
2023-01-02 15:59   ` Christophe Lyon
2023-01-02 23:05     ` Mark Wielaard
2023-01-03 17:29       ` Christophe Lyon
2023-01-04  0:35         ` Mark Wielaard
2023-01-04 10:31           ` Christophe Lyon
2023-01-04 11:07             ` Mark Wielaard
2023-01-09 16:00     ` Christophe Lyon
2023-01-04 12:16   ` Nick Alcock
2023-01-10 12:43     ` Nick Alcock
2023-01-04  3:05 ` Alan Modra
2023-01-04  9:36   ` 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=87mt739186.fsf@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    /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).