c-std-porting.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
	GCC Development <gcc@gcc.gnu.org>,
Subject: Re: C89isms in the test suite
Date: Tue, 15 Nov 2022 05:05:04 +0000	[thread overview]
Message-ID: <0ED99588-AE75-40CA-963F-7032E5035B25@gentoo.org> (raw)
In-Reply-To: <8735amymlt.fsf@oldenburg.str.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 455 bytes --]

> On 14 Nov 2022, at 08:19, Florian Weimer <fweimer@redhat.com> wrote:
> * Sam James:
>> Would you be able to backport 6be2672e4ee41c566a9e072088cccca263bab5f7
>> and 885b6660c17fb91980b5682514ef54668e544b02 to the active <13
>> branches?
> Jakub, okay to backport these two (to 12, 11, 10 I presume)?

(Yes please. It's also given me something to poke at as I didn't log
the failure and only noticed when libasan wasn't installed...)


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]

  reply	other threads:[~2022-11-15  5:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wn8tbmdr.fsf@oldenburg.str.redhat.com>
2022-11-14  4:36 ` C89isms in the test suite Sam James
2022-11-14  8:19   ` Florian Weimer
2022-11-15  5:05     ` Sam James [this message]
2022-11-21 11:12     ` Jakub Jelinek

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0ED99588-AE75-40CA-963F-7032E5035B25@gentoo.org \
    --to=sam@gentoo.org \
    --cc=c-std-porting@lists.linux.dev \
    --cc=fweimer@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \


* 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 NNTP newsgroup(s).