From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Cc: John Wiegley <johnw@newartisans.com>,
Juanma Barranquero <lekktu@gmail.com>
Subject: Re: Fixing compilation and byte-compilation warnings before 25.1
Date: Fri, 13 Nov 2015 15:40:48 +0100 [thread overview]
Message-ID: <5645F670.9040601@online.de> (raw)
In-Reply-To: <m24mgqpt4i.fsf@Vulcan.attlocal.net>
On 13.11.2015 02:47, John Wiegley wrote:
> I'm doing an Emacs build now to test a patch, and it occurs to me how many
> warnings and byte-compilation warnings I'm seeing. I'd like us to resolve as
> many of these warnings as we can before shipping. It makes the build output
> look a bit... unkempt.
>
> Anyone interested in becoming a champion for this cause?
>
> John
>
Hi John,
keeping a reasonable warning-management IMO this is another crucial
point, because people for now get drowned.
Suggest as a first step to abolish all pure warnings, keeping errors
only. I.e. tell if something is broken or very probably broken. Abolish
all pure warnings, style warnings etc.
Then let's establish a policy for warnings - which needs an api, which
didn't exist or was not right when looked into some years ago.
Cheers,
Andreas
next prev parent reply other threads:[~2015-11-13 14:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 1:47 Fixing compilation and byte-compilation warnings before 25.1 John Wiegley
2015-11-13 12:18 ` Juanma Barranquero
2015-11-13 14:40 ` Andreas Röhler [this message]
2015-11-13 15:37 ` Artur Malabarba
2015-11-14 8:34 ` Andreas Röhler
2015-11-13 15:46 ` John Wiegley
2015-11-13 16:22 ` Paul Eggert
2015-11-13 23:00 ` John Wiegley
2015-11-14 5:54 ` daniel sutton
2015-11-14 10:58 ` Michael Heerdegen
2015-11-14 18:22 ` daniel sutton
2015-11-15 12:41 ` Michael Heerdegen
2015-11-16 14:15 ` daniel sutton
2015-11-16 23:24 ` Artur Malabarba
2015-11-15 16:07 ` sea-level rise of byte-compilation warnings [was: Fixing...byte-compilation warnings...] Drew Adams
2015-11-15 16:42 ` daniel sutton
2015-11-15 17:38 ` Drew Adams
2015-11-15 17:47 ` daniel sutton
2015-11-15 22:39 ` Drew Adams
2015-11-16 23:48 ` Artur Malabarba
2015-11-16 23:52 ` Drew Adams
2015-11-17 0:09 ` Artur Malabarba
2015-11-17 15:45 ` Drew Adams
2015-11-17 3:59 ` Ivan Andrus
2015-11-14 15:23 ` Fixing compilation and byte-compilation warnings before 25.1 Andy Moreton
2015-11-14 10:55 ` Stephen Leake
2015-11-14 16:00 ` John Wiegley
2015-11-14 18:01 ` Stephen Leake
2015-11-15 9:08 ` David Engster
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=5645F670.9040601@online.de \
--to=andreas.roehler@online.de \
--cc=emacs-devel@gnu.org \
--cc=johnw@newartisans.com \
--cc=lekktu@gmail.com \
/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).