From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r110242: * lisp/emacs-lisp/cl.el (flet): Fix case of obsolescence message.
Date: Sat, 29 Sep 2012 21:50:44 -0400 [thread overview]
Message-ID: <jwv3920p9e4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <xrbogozjc2.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 29 Sep 2012 16:04:45 -0400")
> Which one wants it capitalized? Both uses places it after a semi-colon.
Indeed, it seems to be more "homogeneous" now. Sorry 'bout the noise.
Stefan
prev parent reply other threads:[~2012-09-30 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1THkk9-0004QF-BP@vcs.savannah.gnu.org>
2012-09-29 2:18 ` [Emacs-diffs] /srv/bzr/emacs/trunk r110242: * lisp/emacs-lisp/cl.el (flet): Fix case of obsolescence message Stefan Monnier
2012-09-29 20:04 ` Glenn Morris
2012-09-30 1:50 ` Stefan Monnier [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=jwv3920p9e4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=rgm@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).