From: Ted Zlatanov <tzz@lifelogs.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r115669: eww: support disabled and readonly text
Date: Mon, 23 Dec 2013 07:00:45 -0500 [thread overview]
Message-ID: <87txdzaiaa.fsf@flea.lifelogs.com> (raw)
In-Reply-To: <jwvob489ubv.fsf-monnier+emacsdiffs@gnu.org> (Stefan Monnier's message of "Sun, 22 Dec 2013 21:26:51 -0500")
On Sun, 22 Dec 2013 21:26:51 -0500 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
>> eww: support disabled and readonly text
SM> Nitpick: "support" should be capitalized (since it starts a sentence)
SM> and the sentence should be punctuated.
Regarding the first nitpick: I saw eww as the first word and didn't want
to capitalize it. But I see both versions in the ChangeLog, from me and
others, e.g.
revno: 114875
committer: Glenn Morris <rgm@gnu.org>
branch nick: trunk
timestamp: Wed 2013-10-30 15:35:14 -0400
message:
htmlfontify.el: remove duplicate Version: header
As for punctuation, the commit log is full of messages like this (not
picking on Chong and Glenn in particular):
revno: 115702
committer: Chong Yidong <cyd@gnu.org>
branch nick: trunk
timestamp: Mon 2013-12-23 11:59:10 +0800
message:
Rename set-temporary-overlay-map -> set-transient-map
...
revno: 115699
committer: Glenn Morris <rgm@gnu.org>
branch nick: trunk
timestamp: Sun 2013-12-22 15:13:18 -0800
message:
Misc small fixes for some recent doc changes
...so I didn't think punctuation was required in the commit message
itself. Could the VC commit message mode add highlighting to show these
problems?
Ted
next prev parent reply other threads:[~2013-12-23 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1VuTME-00023E-Te@vcs.savannah.gnu.org>
2013-12-23 2:26 ` [Emacs-diffs] trunk r115669: eww: support disabled and readonly text Stefan Monnier
2013-12-23 12:00 ` Ted Zlatanov [this message]
2013-12-23 13:54 ` Stefan Monnier
2013-12-23 14:31 ` Ted Zlatanov
2013-12-23 18:54 ` Glenn Morris
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=87txdzaiaa.fsf@flea.lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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.