From: Nicolas Petton <nicolas@petton.fr>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Damien Cassou <damien@cassou.me>, 30039@debbugs.gnu.org
Subject: bug#30039: 26.0.90; [26.1] Making my code warning free is impossible with when-let
Date: Wed, 10 Jan 2018 22:50:40 +0100 [thread overview]
Message-ID: <877esp758v.fsf@petton.fr> (raw)
In-Reply-To: <CAM-tV--8fKwvC0LwoyZK2QfSZErwmLSK50tFuv3Bes__evZ6rQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
Noam Postavsky <npostavs@users.sourceforge.net> writes:
> How about adding a variable which suppresses deprecation warnings from
> a specified version and up. Attached is a work-in-progress patch which
> would allow you to set byte-compile-not-obsolete-since to "25.1" in
> your CI script (or file-locally) and thus ignore deprecation warnings
> from 26.1 or newer.
I think that could be a nice workaround, thanks. What do others think?
Nico
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-01-10 21:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 7:27 bug#30039: 26.0.90; [26.1] Making my code warning free is impossible with when-let Damien Cassou
2018-01-09 8:16 ` Nicolas Petton
2018-01-10 19:11 ` Noam Postavsky
2018-01-10 21:50 ` Nicolas Petton [this message]
2018-01-11 9:19 ` Damien Cassou
2018-01-19 20:00 ` Noam Postavsky
2018-01-19 20:26 ` Eli Zaretskii
2018-01-19 20:40 ` Noam Postavsky
2018-01-20 7:42 ` Eli Zaretskii
2018-01-09 14:05 ` Noam Postavsky
2018-01-09 14:23 ` Damien Cassou
2018-01-09 14:43 ` Noam Postavsky
2018-01-10 12:13 ` Damien Cassou
2018-01-10 15:45 ` Eli Zaretskii
2018-01-10 16:24 ` Nicolas Petton
2018-01-10 17:24 ` Glenn Morris
2018-01-10 18:46 ` Eli Zaretskii
2018-01-10 21:48 ` Nicolas Petton
2018-01-10 22:05 ` Eric Abrahamsen
2018-01-10 22:23 ` Noam Postavsky
2018-01-10 22:40 ` Nicolas Petton
2018-01-10 22:57 ` Eric Abrahamsen
2018-01-10 23:06 ` Noam Postavsky
2018-01-11 0:03 ` Eric Abrahamsen
2018-01-11 9:02 ` Nicolas Petton
2018-04-14 20:17 ` Lars Ingebrigtsen
2018-04-15 11:53 ` Michael Heerdegen
2018-02-21 22:28 ` Michael Heerdegen
2018-02-22 7:42 ` Damien Cassou
2018-03-06 15:12 ` Michael Heerdegen
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=877esp758v.fsf@petton.fr \
--to=nicolas@petton.fr \
--cc=30039@debbugs.gnu.org \
--cc=damien@cassou.me \
--cc=npostavs@users.sourceforge.net \
/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).