all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "John Wiegley" <jwiegley@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Richard Stallman <rms@gnu.org>, 21953@debbugs.gnu.org
Subject: bug#21953: Eliminate warnings in the emacs-25 release branch
Date: Thu, 19 Nov 2015 09:37:16 -0800	[thread overview]
Message-ID: <m2si416gc3.fsf@newartisans.com> (raw)
In-Reply-To: <564E0708.8090600@yandex.ru> (Dmitry Gutov's message of "Thu, 19 Nov 2015 19:29:44 +0200")

>>>>> Dmitry Gutov <dgutov@yandex.ru> writes:

> I can get behind taking care of "correctness" warnings, but if we lose the
> obsolete functions warnings, we risk forgetting to take care of their
> causes.
> 
> And it's not like we can actually fix all instances of obsolete usages
> before the current release: a significant part of the warnings comes from
> gnus, org, cc-mode and calendar, all of which, I'm assuming, have to support
> older Emacsen.

If that's the case, I'm willing to filter those from the final count before
closing this issue. Then, in 25.2, we can focus on eliminating those as well.

> We _should_ be able to take care of CEDET warnings, but probably after their
> development migrates here.

That's good to hear; but can that happen for 25.1? CEDET is rather egregious
in the warnings category right now. If that means suppressing warnings
throughout CEDET for this release, I'm OK with that as a temporary measure.

By 25.2, anything that is built using "make" should be warning free, both C
and Emacs Lisp, using whatever reference platform we define as the litmus
test. I'll be building on that platform regularly, to report new warnings.

John





  reply	other threads:[~2015-11-19 17:37 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 [this message]
2015-11-19 17:46         ` Dmitry Gutov
2015-11-19 17:54         ` Eli Zaretskii
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2si416gc3.fsf@newartisans.com \
    --to=jwiegley@gmail.com \
    --cc=21953@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.