From: Paul Eggert <eggert@cs.ucla.edu>
To: Alex Gramiak <agrambot@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Checking all C warning flags at once during configuration
Date: Wed, 1 May 2019 11:31:46 -0700 [thread overview]
Message-ID: <3291f25d-ed8f-3b2f-dc41-a18334edfee5@cs.ucla.edu> (raw)
In-Reply-To: <87tveem3pr.fsf@gmail.com>
On 5/1/19 11:25 AM, Alex Gramiak wrote:
> Would you happen to know why the argument is always empty in the
> commented out loop?
Sorry, not offhand by just looking at the patch.
> Should I post
> this to the Gnulib mailing list at this stage?
That's a more-appropriate list for such a patch, yes. Please try to make
your email self-contained. bug-gnulib is less populated-than emacs-devel
so I wouldn't expect an overwhelming response. What would help is a
sample use and timing statistics to motivate other readers to look into it.
next prev parent reply other threads:[~2019-05-01 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 14:53 Checking all C warning flags at once during configuration Alex Gramiak
2019-04-29 19:39 ` Paul Eggert
2019-04-30 18:52 ` Alex Gramiak
2019-04-30 19:38 ` Paul Eggert
2019-05-01 18:25 ` Alex Gramiak
2019-05-01 18:31 ` Paul Eggert [this message]
2019-05-01 23:13 ` Alex Gramiak
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3291f25d-ed8f-3b2f-dc41-a18334edfee5@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=agrambot@gmail.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).