From: Simon Marchi <simon.marchi@efficios.com>
To: Christian Biesinger <cbiesinger@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 3/3] Add -Wstrict-null-sentinel to gdbsupport/warning.m4
Date: Mon, 10 Feb 2020 16:46:00 -0000 [thread overview]
Message-ID: <baa98807-f22d-65f1-be25-f12e52ebd3f1@efficios.com> (raw)
In-Reply-To: <CAPTJ0XGFpk_GMmV4J9nribYE1D8=LRb-LzUXWck6E95vvNCTkA@mail.gmail.com>
On 2020-02-10 11:42 a.m., Christian Biesinger wrote:
> Any thoughts on instead dong:
> +-Wstrict-null-sentinel \
> +"
>
> so that future changes don't need to change the last line? Helps with blame too.
Sure, I I'll do that. I like when we use a comma after the last enumerator in enums
too, for the same reason.
Simon
next prev parent reply other threads:[~2020-02-10 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 16:40 [PATCH 1/3] gdbsupport: use AM_GDB_WARNINGS Simon Marchi
2020-02-10 16:40 ` [PATCH 3/3] Add -Wstrict-null-sentinel to gdbsupport/warning.m4 Simon Marchi
2020-02-10 16:42 ` Christian Biesinger via gdb-patches
2020-02-10 16:46 ` Simon Marchi [this message]
2020-02-11 14:57 ` Tom Tromey
2020-02-11 16:11 ` Simon Marchi
2020-02-10 16:40 ` [PATCH 2/3] Move gdb/warning.m4 to gdbsupport Simon Marchi
2020-02-11 14:55 ` Tom Tromey
2020-02-11 14:55 ` [PATCH 1/3] gdbsupport: use AM_GDB_WARNINGS Tom Tromey
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=baa98807-f22d-65f1-be25-f12e52ebd3f1@efficios.com \
--to=simon.marchi@efficios.com \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox