From: Paul Eggert <eggert@cs.ucla.edu>
To: Daniel Colascione <dancol@dancol.org>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r117013: Merge from emacs-24; up to r117008
Date: Tue, 22 Apr 2014 14:38:58 -0700 [thread overview]
Message-ID: <5356E172.1000702@cs.ucla.edu> (raw)
In-Reply-To: <5356E089.1000702@dancol.org>
On 04/22/2014 02:35 PM, Daniel Colascione wrote:
> It looks like you re-introduced the cl-loop destructuring bug.
Ah, sorry, I'll take a look at that as soon as I can but won't be able
to look at it for an hour or so. Since it's something you're expert in
(I'm not....) any advice would be appreciated.
next prev parent reply other threads:[~2014-04-22 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1WciJU-0001lo-9L@vcs.savannah.gnu.org>
2014-04-22 21:35 ` [Emacs-diffs] trunk r117013: Merge from emacs-24; up to r117008 Daniel Colascione
2014-04-22 21:38 ` Paul Eggert [this message]
2014-04-22 21:39 ` Daniel Colascione
2014-04-22 21:49 ` Daniel Colascione
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=5356E172.1000702@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=dancol@dancol.org \
--cc=emacs-devel@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 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).