From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: dgutov@yandex.ru, rms@gnu.org, 21953@debbugs.gnu.org
Subject: bug#21953: Eliminate warnings in the emacs-25 release branch
Date: Thu, 19 Nov 2015 19:54:25 +0200 [thread overview]
Message-ID: <83a8q998oe.fsf@gnu.org> (raw)
In-Reply-To: <m2si416gc3.fsf@newartisans.com>
> From: "John Wiegley" <jwiegley@gmail.com>
> Date: Thu, 19 Nov 2015 09:37:16 -0800
> Cc: Richard Stallman <rms@gnu.org>, 21953@debbugs.gnu.org
>
> By 25.2, anything that is built using "make" should be warning free, both C
> and Emacs Lisp
We can stop worrying about warnings in C: there are none, and a few
people regularly compile with pedantic compiler switches and fix
whatever they flag.
The problem of warnings is limited to Lisp, and then mostly to a few
specific packages. Dmitry mentioned some of them. From my POV, the
worst barrage is in CEDET, so IMO that should be the place where we
apply the first efforts.
next prev parent reply other threads:[~2015-11-19 17:54 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 17:44 bug#21953: Eliminate warnings in the emacs-25 release branch John Wiegley
2015-11-18 17:58 ` Eli Zaretskii
2015-11-18 18:04 ` Dmitry Gutov
2015-11-18 18:17 ` Glenn Morris
2015-11-18 18:44 ` Eli Zaretskii
2015-11-23 19:10 ` Glenn Morris
2015-11-23 22:04 ` John Wiegley
2015-11-23 22:47 ` Drew Adams
2015-11-24 3:30 ` Eli Zaretskii
2015-11-24 3:40 ` John Wiegley
2015-11-24 17:40 ` Glenn Morris
2015-11-25 1:03 ` John Wiegley
2015-11-18 19:09 ` Artur Malabarba
2015-11-18 20:36 ` Eli Zaretskii
2015-11-18 20:57 ` Artur Malabarba
2015-11-19 2:06 ` John Wiegley
2015-11-19 17:20 ` Stephen Leake
2015-11-19 17:29 ` Dmitry Gutov
2015-11-19 17:37 ` John Wiegley
2015-11-19 17:46 ` Dmitry Gutov
2015-11-19 17:54 ` Eli Zaretskii [this message]
2015-11-19 18:18 ` John Wiegley
2015-11-19 18:34 ` Juanma Barranquero
2015-11-19 19:05 ` John Wiegley
2015-11-19 20:29 ` Eli Zaretskii
2015-11-19 20:25 ` Eli Zaretskii
2015-11-19 20:31 ` Juanma Barranquero
2015-11-19 20:51 ` Eli Zaretskii
2015-11-20 0:26 ` Juanma Barranquero
2015-11-25 20:58 ` Andy Moreton
2015-11-26 17:55 ` Eli Zaretskii
2015-11-19 20:01 ` David Engster
2015-11-19 20:26 ` John Wiegley
2015-11-19 20:32 ` Eli Zaretskii
2015-11-20 10:41 ` Stephen Leake
2015-11-19 17:45 ` Eli Zaretskii
2015-11-18 18:39 ` Ken Brown
2015-11-18 18:52 ` Eli Zaretskii
2015-11-18 19:19 ` Ken Brown
2015-11-18 20:38 ` Eli Zaretskii
2015-11-18 20:57 ` Stephen Berman
[not found] ` <mailman.233.1447954214.31583.bug-gnu-emacs@gnu.org>
2015-11-24 19:55 ` Alan Mackenzie
2015-11-25 0:28 ` Dmitry Gutov
2015-11-25 9:31 ` Alan Mackenzie
2015-11-25 14:36 ` Dmitry Gutov
2015-11-25 15:50 ` Alan Mackenzie
2015-11-25 18:54 ` Glenn Morris
2015-11-26 8:33 ` Andreas Röhler
2015-11-26 15:51 ` Eli Zaretskii
2015-11-28 18:44 ` John Wiegley
2015-11-29 9:13 ` Andreas Röhler
2015-11-30 0:38 ` Richard Stallman
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=83a8q998oe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21953@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=jwiegley@gmail.com \
--cc=rms@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).