public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: binutils@sourceware.org
Subject: 2.42 branch has been created
Date: Mon, 15 Jan 2024 15:28:24 +0000	[thread overview]
Message-ID: <87v87u39bb.fsf@redhat.com> (raw)

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.
    * 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
  


             reply	other threads:[~2024-01-15 15:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 15:28 Nick Clifton [this message]
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
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=87v87u39bb.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).