all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 11862@debbugs.gnu.org, rms@gnu.org
Subject: bug#11862: [PATCH 9/9] doc/lispref/intro.texi: Use passive voice
Date: Thu, 05 Jul 2012 19:37:55 +0300	[thread overview]
Message-ID: <83txxm2mfw.fsf@gnu.org> (raw)
In-Reply-To: <87bojuxq1l.fsf@nolde.home>

> From: Stephen Berman <stephen.berman@gmx.net>
> Date: Thu, 05 Jul 2012 16:04:22 +0200
> Cc: 11862@debbugs.gnu.org
> 
> On Thu, 05 Jul 2012 06:14:00 -0400 Richard Stallman <rms@gnu.org> wrote:
> 
> >      The value of this variable is the version of Emacs being run.  It is a
> >      string such as @code{"23.1.1"}.  The last number in this string is not
> >      really part of the Emacs release version number; it is incremented
> >     -each time you build Emacs in any given directory.  A value with four
> >     +each time Emacs is built in any given directory.
> >
> > Please use the active voice by preference.
> > For instance, you could write it this:
> >
> >    each time you build Emacs in a given directory, that increments this number.
> 
> This sounds rather awkward to me.  Would you accept "it gets
> incremented" as a "more active passive" alternative?

I think there's a better alternative that is entirely active:

  each build of Emacs in any given directory increments that number.

> Aside from style, the statement is inaccurate, isn't it?  At least
> with "make bootstrap" the last number is always 1.

Yes.  So:

   The value of this variable is the version of Emacs being run.  It
   is a string such as @code{"23.1.1"}.  The last number in this
   string is not really part of the Emacs release version number; it
   starts at 1, is reset to 1 by @kbd{make bootstrap}, and each build
   of Emacs increments that number.





  reply	other threads:[~2012-07-05 16:37 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 20:15 bug#11862: [PATCH 0/9] doc/lispref/intro.texi: Copyediting Michael Witten
2012-07-04 20:15 ` bug#11862: [PATCH 1/9] doc/lispref/intro.texi: Offset modifier with a comma Michael Witten
2012-07-05 10:13   ` Richard Stallman
2012-07-05 16:52     ` bug#11862: [PATCH 1/9] doc/lispref/intro.texi: Offset modifier Michael Witten
2012-07-04 20:15 ` bug#11862: [PATCH 2/9] doc/lispref/intro.texi: `can' -> `may' Michael Witten
2012-07-05 10:13   ` Richard Stallman
2012-07-04 20:15 ` bug#11862: [PATCH 3/9] doc/lispref/intro.texi: Eradicate that pesky future tense Michael Witten
2012-07-05 10:13   ` Richard Stallman
2012-07-04 20:15 ` bug#11862: [PATCH 4/9] doc/lispref/intro.texi: More precise language Michael Witten
2012-07-05 10:13   ` Richard Stallman
2012-07-04 20:15 ` bug#11862: [PATCH 5/9] doc/lispref/intro.texi: Use singular form in a sentence Michael Witten
2012-07-04 20:15 ` bug#11862: [PATCH 6/9] doc/lispref/intro.texi: Re-fill a paragraph Michael Witten
2012-07-04 20:15 ` bug#11862: [PATCH 7/9] doc/lispref/intro.texi: `optional' -> `&optional'; Michael Witten
2012-07-05  3:03   ` Glenn Morris
2012-07-04 20:15 ` bug#11862: [PATCH 8/9] doc/lispref/intro.texi: More precise language for Michael Witten
2012-07-05 21:50   ` Richard Stallman
2012-07-05 22:55     ` bug#11862: [PATCH 8/9 v2] doc/lispref/intro.texi: More precise language for what a variable is Michael Witten
2012-07-06  1:58       ` bug#11862: [PATCH 8/9 v2] doc/lispref/intro.texi: More preciselanguage " Drew Adams
2012-07-06  8:07         ` bug#11862: [PATCH 8/9 v3] doc/lispref/intro.texi: More precise language " Michael Witten
2012-07-06 15:55           ` Wolfgang Jenkner
2012-07-06 16:45             ` Drew Adams
2012-07-06 20:06               ` bug#11862: Splitting and simplifying [PATCH 8/9] Michael Witten
2012-07-06 20:17                 ` bug#11862: [PATCH 8a/9] doc/lispref/intro.texi: Introduce the term `value' early on Michael Witten
2012-07-06 20:18                 ` bug#11862: [PATCH 8b/2] doc/lispref/intro.texi: Reduce and reorganize node `A sample Variable Description' Michael Witten
2012-07-07  9:18             ` bug#11862: [PATCH 8/9 v3] doc/lispref/intro.texi: More precise language for what a variable is Richard Stallman
2012-07-08  4:41           ` bug#11862: [Copyright assignment] Chong Yidong
2012-07-06  6:40       ` bug#11862: [PATCH 8/9 v2] doc/lispref/intro.texi: More precise language for what a variable is Eli Zaretskii
2012-07-04 20:16 ` bug#11862: [PATCH 9/9] doc/lispref/intro.texi: Use passive voice Michael Witten
2012-07-05 10:14   ` Richard Stallman
2012-07-05 14:04     ` Stephen Berman
2012-07-05 16:37       ` Eli Zaretskii [this message]
2012-07-05 16:59         ` Glenn Morris
2012-07-05 17:14         ` Michael Witten
2012-07-05 19:09           ` Stephen Berman
2012-07-05  2:52 ` bug#11862: [PATCH 0/9] doc/lispref/intro.texi: Copyediting Stefan Monnier
     [not found]   ` <CAMOZ1BsRkioUhGGOuFrmbkMRnJiQ6h=tviNODS11BjG3_jYVbA@mail.gmail.com>
2012-07-05  7:09     ` 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=83txxm2mfw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=11862@debbugs.gnu.org \
    --cc=rms@gnu.org \
    --cc=stephen.berman@gmx.net \
    /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.