From: John Levon <john.levon@joyent.com>
To: smatch@vger.kernel.org
Cc: John Levon <john.levon@joyent.com>
Subject: [PATCH] Remove bogus option from sparse manual.
Date: Wed, 13 Nov 2019 16:50:59 +0000 [thread overview]
Message-ID: <1573663859-9854-1-git-send-email-john.levon@joyent.com> (raw)
-Wempty-character-constant was removed.
---
sparse.1 | 7 -------
1 file changed, 7 deletions(-)
diff --git a/sparse.1 b/sparse.1
index 9a622ab2..beb48442 100644
--- a/sparse.1
+++ b/sparse.1
@@ -244,13 +244,6 @@ Sparse issues these warnings by default. To turn them off, use
\fB\-Wno\-enum\-mismatch\fR.
.
.TP
-.B \-Wempty\-character\-constant
-Warn about a constant such as ''.
-
-Sparse issues these warnings by default. To turn them off, use
-\fB\-Wno\-empty\-character\-constant\fR.
-.
-.TP
.B \-Winit\-cstring
Warn about initialization of a char array with a too long constant C string.
--
2.17.1
reply other threads:[~2019-11-13 16:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1573663859-9854-1-git-send-email-john.levon@joyent.com \
--to=john.levon@joyent.com \
--cc=smatch@vger.kernel.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