public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: The 2.40 branch has been created
Date: Wed, 4 Jan 2023 09:36:39 +0000	[thread overview]
Message-ID: <6add9816-203c-85a9-8992-d2a14041dc2c@redhat.com> (raw)
In-Reply-To: <Y7Ts8WLs3ahq2/Pv@squeak.grove.modra.org>

Hi Alan,

> Would you like me to apply the copyright year update to the branch?

Yes please.  (I should have thought of this and delayed branching until
after the start of the new year.  Doh).

> Also, the libiberty update should have merged gcc's config/picflag.m4
> with ours, in order for libiberty/configure to regen without
> differences on the branch.  I'm going to apply the following mainline,
> and will backport to the branch if that's OK?

Totally OK, please do.

Aside - keeping our version of libiberty in sync with gcc, but with
local tweaks is becoming burdensome...

Cheers
   Nick


      reply	other threads:[~2023-01-04  9:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31 13:00 Nick Clifton
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 [this message]

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=6add9816-203c-85a9-8992-d2a14041dc2c@redhat.com \
    --to=nickc@redhat.com \
    --cc=amodra@gmail.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).