From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/gdbserver: switch to AC_CONFIG_MACRO_DIRS
Date: Thu, 24 Jun 2021 19:45:32 +0100 [thread overview]
Message-ID: <96320ece-2976-2b3e-405e-7b7d339ab8ed@palves.net> (raw)
In-Reply-To: <YNO1L+uADd9tAYSX@vapier>
On 2021-06-23 11:26 p.m., Mike Frysinger wrote:
> On 23 Jun 2021 10:38, Pedro Alves wrote:
>> On 2021-06-18 5:38 a.m., Mike Frysinger via Gdb-patches wrote:
>>>
>>> how about at the top of acinclude.m4:
>>> dnl NB: When possible, try to avoid explicit includes of ../config/ files.
>>> dnl They're normally found by aclocal automatically and recorded in aclocal.m4.
>>> dnl However, some are kept here explicitly to silence harmless warnings from
>>> dnl aclocal when it finds AM_xxx macros via local search paths instead of
>>> dnl system search paths.
>>> -mike
>>
>> That seems good to me, but I think better would be to put all such include lines
>> together and put the comment right on top of that section. Like:
>>
>> dnl NB: When possible, we try to avoid explicit includes of ../config/ files.
>> dnl They're normally found by aclocal automatically and recorded in aclocal.m4.
>> dnl However, the following are kept here explicitly to silence harmless warnings
>> dnl from aclocal when it finds AM_xxx macros via local search paths instead of
>> dnl system search paths.
>> m4_include([../config/foo.m4])
>> m4_include([../config/bar.m4])
>>
>>
>> I've had my share of "comments at the top" that I've missed in the past...
>
> how about:
>
LGTM, thanks. I'd still suggest tweaking the comments to make it clearer
that by "some are kept" we're talking about the ones right below
the comment, like say, "these below are kept" instead or something like that.
Pedro Alves
next prev parent reply other threads:[~2021-06-24 18:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 1:24 [PATCH] gdb: add ../config/pkg.m4 in acinclude.m4 Simon Marchi via Gdb-patches
2021-05-09 20:00 ` Mike Frysinger via Gdb-patches
2021-05-10 0:16 ` Simon Marchi via Gdb-patches
2021-05-10 1:14 ` Mike Frysinger via Gdb-patches
2021-05-10 1:32 ` Simon Marchi via Gdb-patches
2021-05-10 13:25 ` Tom Tromey
2021-05-10 22:36 ` Mike Frysinger via Gdb-patches
2021-06-15 5:44 ` [PATCH] gdb/gdbserver: switch to AC_CONFIG_MACRO_DIRS Mike Frysinger via Gdb-patches
2021-06-17 2:30 ` Simon Marchi via Gdb-patches
2021-06-17 4:21 ` Mike Frysinger via Gdb-patches
2021-06-17 14:43 ` Simon Marchi via Gdb-patches
2021-06-18 4:38 ` Mike Frysinger via Gdb-patches
2021-06-18 13:22 ` Simon Marchi via Gdb-patches
2021-06-23 9:38 ` Pedro Alves
2021-06-23 22:26 ` Mike Frysinger via Gdb-patches
2021-06-24 18:45 ` Pedro Alves [this message]
2021-06-18 14:03 ` [PATCH v2] " Mike Frysinger via Gdb-patches
2021-06-20 0:48 ` Simon Marchi via Gdb-patches
2021-06-20 2:10 ` Mike Frysinger via Gdb-patches
2021-06-20 2:17 ` Simon Marchi via Gdb-patches
2021-06-20 2:22 ` [PATCH v3] " Mike Frysinger via Gdb-patches
2021-06-20 2:46 ` Simon Marchi via Gdb-patches
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=96320ece-2976-2b3e-405e-7b7d339ab8ed@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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