From: Xue Fuqiao <xfq.free@gmail.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] trunk r113589: Merge: Add vc-ignore.
Date: Tue, 30 Jul 2013 14:10:30 +0800 [thread overview]
Message-ID: <CAAF+z6GaF=jV9sCYaWD0DHDjOEX9=5SrQbgOQ4zoM8pD6Dh_=Q@mail.gmail.com> (raw)
In-Reply-To: <87mwp4odfx.fsf@uwakimon.sk.tsukuba.ac.jp>
On Tue, Jul 30, 2013 at 12:54 PM, Stephen J. Turnbull
<stephen@xemacs.org> wrote:
> Xue Fuqiao writes:
> > On Tue, Jul 30, 2013 at 9:23 AM, Stefan Monnier
> > <monnier@iro.umontreal.ca> wrote:
> > >> + (cvs-append-to-ignore): Moved from pcvs.el.
> > >
> > > Please use the present tense in ChangeLog entries.
> >
> > So, what should it be? Is "Moving from pcvs.el" appropriate? My
> > grammar isn't very good.
>
> "Move here from pcvs.el." would be good.
>
> "Moving" is the "present participle", not the present tense. The idea
> is to use the simple present tense to describe the change (not what
> was lacking) and to indicate what the developer was thinking when he
> executed the change. If this is done consistently, there's no
> confusion between undesirable (pre-change) states and corrected
> states. Native speakers often use past tense to describe the buggy
> state: "Emacs crashed when user did X", with "change Y fixes this"
> implied. But it's hard (for a native speaker) to write "Emacs crashes
> ..." when it's already fixed. So the discipline of use present tense
> tends to implicitly enforce the discipline of describing the change,
> not the bug.
Fixed, thanks. Maybe it can be added to standards.texi.
--
Best regards, Xue Fuqiao.
http://www.gnu.org/software/emacs/
prev parent reply other threads:[~2013-07-30 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1V3xqp-00062F-PG@vcs.savannah.gnu.org>
2013-07-30 1:23 ` [Emacs-diffs] trunk r113589: Merge: Add vc-ignore Stefan Monnier
2013-07-30 3:53 ` Xue Fuqiao
2013-07-30 4:54 ` Stephen J. Turnbull
2013-07-30 6:10 ` Xue Fuqiao [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='CAAF+z6GaF=jV9sCYaWD0DHDjOEX9=5SrQbgOQ4zoM8pD6Dh_=Q@mail.gmail.com' \
--to=xfq.free@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stephen@xemacs.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).