From: npostavs@users.sourceforge.net
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 20636@debbugs.gnu.org, "Johan Bockgård" <bojohan@gnu.org>
Subject: bug#20636: 24.5; pcase: nil should be an UPattern
Date: Thu, 30 Jun 2016 22:42:37 -0400 [thread overview]
Message-ID: <87k2h6hyea.fsf@users.sourceforge.net> (raw)
In-Reply-To: <CAArVCkRioJT-xOUY0u7uf+efpA80CLpRL1wGTGM2VwjiyqL0Kg@mail.gmail.com> (Philipp Stephani's message of "Sun, 24 May 2015 11:00:03 +0000")
tags 20636 wontfix
close 20636
quit
In 20784 it was decided to that nil and t should not be valid patterns
at all (t is still supported as a match-all, but deprecated).
prev parent reply other threads:[~2016-07-01 2:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 18:27 bug#20636: 24.5; pcase: nil should be an UPattern Philipp Stephani
2015-05-24 0:25 ` Johan Bockgård
2015-05-24 11:00 ` Philipp Stephani
2016-07-01 2:42 ` npostavs [this message]
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=87k2h6hyea.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=20636@debbugs.gnu.org \
--cc=bojohan@gnu.org \
--cc=p.stephani2@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).