all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Damien Cassou <damien@cassou.me>
Cc: 30039@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#30039: 26.0.90; [26.1] Making my code warning free is impossible with when-let
Date: Wed, 10 Jan 2018 17:45:49 +0200	[thread overview]
Message-ID: <83bmi167ki.fsf@gnu.org> (raw)
In-Reply-To: <87d12hq5c7.fsf@cassou.me> (message from Damien Cassou on Wed, 10 Jan 2018 13:13:44 +0100)

> From: Damien Cassou <damien@cassou.me>
> Date: Wed, 10 Jan 2018 13:13:44 +0100
> Cc: 30039@debbugs.gnu.org
> 
> Noam Postavsky <npostavs@users.sourceforge.net> writes:
> > Since we don't have a time machine, this seems impractical (or if you
> > mean release 25.4 just for this, kind of overkill).
> 
> 
> I would also like a time machine but I was more referring to a new
> release of Emacs 25.

You mean, release Emacs 25.4 with this single change?  That's unlikely
to happen.  And even if it did, I don't understand what problem would
it solve: people who have previous versions will still need to
upgrade, and you can tell them to upgrade to Emacs 26.1 exactly as you
can tell them to upgrade to 25.4.  What am I missing?

> >> - un-deprecate when-let (and if-let) in Emacs 26 and re-deprecate it
> >>   later.
> >
> > When is "later"?  Wouldn't the problem remain indefinitely?
> 
> That’s a question we need to answer. I think supporting 2 releases would
> already be good (i.e., 26.1 does not deprecate but 26.2 does).

That's not how we deprecate stuff.  We never wait with deprecation,
only with the actual removal.





  reply	other threads:[~2018-01-10 15:45 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=83bmi167ki.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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 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.