From: Mark Oteiza <mvoteiza@udel.edu>
To: Richard Stallman <rms@gnu.org>
Cc: 25523@debbugs.gnu.org
Subject: bug#25523: 25.1; [PATCH] rename `cl-caddr' etc. to `caddr' etc.
Date: Wed, 25 Jan 2017 14:29:44 -0500 [thread overview]
Message-ID: <20170125192944.GA3405@holos.localdomain> (raw)
In-Reply-To: <E1cWS50-0005MG-6g@fencepost.gnu.org>
On 25/01/17 at 01:13pm, Richard Stallman wrote:
> Remember that we need to change the Emacs Lisp Reference Manual too.
Pushed as 43eba49
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=43eba49
next prev parent reply other threads:[~2017-01-25 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 2:18 bug#25523: 25.1; rename `cl-caddr' etc. to `caddr' etc Drew Adams
2017-01-25 4:57 ` bug#25523: 25.1; [PATCH] " Mark Oteiza
2017-01-25 18:13 ` Richard Stallman
2017-01-25 19:29 ` Mark Oteiza [this message]
2017-01-25 19:43 ` Drew Adams
2017-01-25 19:46 ` Lars Ingebrigtsen
2017-01-25 22:39 ` Glenn Morris
2017-02-08 4:48 ` npostavs
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=20170125192944.GA3405@holos.localdomain \
--to=mvoteiza@udel.edu \
--cc=25523@debbugs.gnu.org \
--cc=rms@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).