From: "François Dumont" <frs.dumont@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: rs2740@gmail.com, libstdc++ <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] [11/12/13/14 Regression] ABI break in _Hash_node_value_base since GCC 11 [PR 111050]
Date: Thu, 28 Sep 2023 19:25:24 +0200 [thread overview]
Message-ID: <8e8a8648-9e75-8b9a-b3a4-664695fa2690@gmail.com> (raw)
In-Reply-To: <CACb0b4=_B2vJD6=dPoCMQ-Fh=XX1x-XAVn1yG0i6tYFHiYFU5g@mail.gmail.com>
On 28/09/2023 18:18, Jonathan Wakely wrote:
> On Wed, 27 Sept 2023 at 05:44, François Dumont <frs.dumont@gmail.com> wrote:
>> Still no chance to get feedback from TC ? Maybe I can commit the below
>> then ?
> I've heard back from Tim now. Please use "Tim Song
> <t.canens.cpp@gmail.com>" as the author.
>
> You can change the commit again using git commit --amend --author "Tim
> Song <t.canens.cpp@gmail.com>"
Sure :-)
>
> OK for trunk with that change - thanks for waiting.
Committed to trunk, let me know for backports.
>> AFAICS on gcc mailing list several gcc releases were done recently, too
>> late.
> There have been no releases this month, so the delay hasn't caused any problems.
I was confused by emails like this one:
https://gcc.gnu.org/pipermail/gcc/2023-September/242429.html
I just subscribed to gcc mailing list, I had no idea there were regular
snapshots like this.
next prev parent reply other threads:[~2023-09-28 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 13:56 François Dumont
2023-09-10 15:36 ` Sam James
2023-09-11 11:51 ` Jonathan Wakely
2023-09-11 17:19 ` François Dumont
2023-09-12 16:09 ` Jonathan Wakely
2023-09-14 4:46 ` François Dumont
2023-09-27 4:44 ` François Dumont
2023-09-28 16:18 ` Jonathan Wakely
2023-09-28 17:25 ` François Dumont [this message]
2023-09-29 9:53 ` Jonathan Wakely
2023-10-02 20:51 ` François Dumont
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=8e8a8648-9e75-8b9a-b3a4-664695fa2690@gmail.com \
--to=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=rs2740@gmail.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).