From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Xue Fuqiao <xfq.free@gmail.com>, 14750@debbugs.gnu.org
Subject: bug#14750: [PATCH] Cleanup for "commit message"
Date: Mon, 01 Jul 2013 15:46:32 -0400 [thread overview]
Message-ID: <vpip0u9i7b.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvhage13nn.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 01 Jul 2013 15:29:14 -0400")
Stefan Monnier wrote:
> But after that I think it makes sense to pick one term and stick to it.
AFAICS, we do. A quick grep of doc/ suggests at present "commit message"
is only used in a tiny number of places in pcl-cvs.texi and gnus.texi.
prev parent reply other threads:[~2013-07-01 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 3:16 bug#14750: [PATCH] Cleanup for "commit message" Xue Fuqiao
2013-07-01 0:19 ` Glenn Morris
2013-07-01 19:29 ` Stefan Monnier
2013-07-01 19:46 ` Glenn Morris [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=vpip0u9i7b.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=14750@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=xfq.free@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).