From: Paul Eggert <eggert@cs.ucla.edu>
To: Martin Sebor <msebor@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v3] remove attribute access from regexec
Date: Fri, 27 Aug 2021 11:57:39 -0700 [thread overview]
Message-ID: <e18a4bf8-5847-f886-3b19-f968c8a64cbf@cs.ucla.edu> (raw)
In-Reply-To: <9b9247b6-2839-906b-3ed1-acf3651c178f@gmail.com>
On 8/27/21 9:34 AM, Martin Sebor wrote:
> It includes quite a few
> changes that don't seem necessary to avoid the GCC warning (BZ #28170)
True. However, the changes have been tested on the Gnulib side, and I
feel more comfortable applying them all than doing just some of them.
It's less work anyway; and the more-work option feels like make-work.
I'll give people more time to comment before installing.
next prev parent reply other threads:[~2021-08-27 18:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 18:26 [PATCH] " Martin Sebor
2021-08-13 20:11 ` Paul Eggert
2021-08-13 21:30 ` Martin Sebor
2021-08-13 22:34 ` Paul Eggert
2021-08-14 20:08 ` Martin Sebor
2021-08-18 15:53 ` [PATCH v2] " Martin Sebor
2021-08-18 19:52 ` [PATCH] " Paul Eggert
2021-08-19 23:50 ` [PATCH v3] " Martin Sebor
2021-08-22 5:06 ` Paul Eggert
2021-08-26 15:06 ` Martin Sebor
2021-08-26 16:24 ` Paul Eggert
2021-08-26 16:47 ` Martin Sebor
2021-08-27 8:52 ` Paul Eggert
2021-08-27 16:34 ` Martin Sebor
2021-08-27 17:50 ` Allow #pragma GCC in headers in conformtest [committed] (was: Re: [PATCH v3] remove attribute access from regexec) Joseph Myers
2021-08-27 18:57 ` Paul Eggert [this message]
2021-09-20 20:46 ` [PATCH v3] remove attribute access from regexec Joseph Myers
2021-09-21 6:52 ` Paul Eggert
2021-09-21 13:48 ` Joseph Myers
2021-09-21 15:00 ` Paul Eggert
2021-10-19 16:39 ` Carlos O'Donell
2021-10-19 17:06 ` Martin Sebor
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=e18a4bf8-5847-f886-3b19-f968c8a64cbf@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
--cc=msebor@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).