From: Noam Postavsky <npostavs@gmail.com>
To: Pip Cet <pipcet@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, 36321@debbugs.gnu.org
Subject: bug#36321: Error: Forgot to expand macro pcase--flip in (pcase--flip memql '(2 1) val)
Date: Sun, 14 Jul 2019 10:39:15 -0400 [thread overview]
Message-ID: <87a7dg1y0c.fsf@gmail.com> (raw)
In-Reply-To: <CAOqdjBeiAzTu=dJiuahajD1F2ei5+95LD=G97CPD6TckA1q15Q@mail.gmail.com> (Pip Cet's message of "Thu, 4 Jul 2019 21:00:27 +0000")
forcemerge 36447 36321
quit
Pip Cet <pipcet@gmail.com> writes:
> On Thu, Jul 4, 2019 at 8:25 PM Noam Postavsky <npostavs@gmail.com> wrote:
>> Andreas Schwab <schwab@linux-m68k.org> writes:
>> > The error was introduced between
>> > 8b379bbeca9b3765e2b1e948d9d9c90ab92ff4b6 and
>> > 869cf5cbc0721bbe9e4df557f4ed3633fb13c05f
>>
>> I don't see anything plausible in that range. I wonder if this could be
>> the same as Bug#36447.
>
> I rather suspect it is, too. Can we get our hands on an emacs binary
> and an emacs.pdmp file from a failing build?
By the timing of when this error popped up, I'm going to say it's most
likely the same as 36447, so I'll go ahead and merge them. It should be
fixed now, but if the error ever happens again, we'll know it's actually
something else.
prev parent reply other threads:[~2019-07-14 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 10:23 bug#36321: Error: Forgot to expand macro pcase--flip in (pcase--flip memql '(2 1) val) Andreas Schwab
2019-06-21 10:40 ` Noam Postavsky
2019-06-21 12:36 ` Andreas Schwab
2019-06-23 9:16 ` Andreas Schwab
2019-06-23 9:36 ` Andreas Schwab
2019-07-04 20:24 ` Noam Postavsky
2019-07-04 21:00 ` Pip Cet
2019-07-14 14:39 ` Noam Postavsky [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7dg1y0c.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=36321@debbugs.gnu.org \
--cc=pipcet@gmail.com \
--cc=schwab@linux-m68k.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.