From: Van L <van@scratch.space>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32037@debbugs.gnu.org
Subject: bug#32037: simplify possessive form's "functions' definitions"
Date: Tue, 3 Jul 2018 01:35:23 +1000 [thread overview]
Message-ID: <47C8A142-D5EE-49D0-8C91-CE2A28694D99@scratch.space> (raw)
In-Reply-To: <83r2klk5zw.fsf@gnu.org>
> Thanks, but AFAIK the original wording is perfectly correct English
> (if not more correct). Why did you think it needed to be changed?
Is it the correct Emacs’ or Emacs’s? which is recommended use?
The suggestion here is less pedantic.
next prev parent reply other threads:[~2018-07-02 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 15:11 bug#32037: simplify possessive form's "functions' definitions" Van L
2018-07-02 15:32 ` Eli Zaretskii
2018-07-02 15:35 ` Van L [this message]
2018-07-02 16:24 ` Eli Zaretskii
2018-07-02 17:19 ` Glenn Morris
2018-07-02 19:59 ` Robert Pluim
2018-07-04 16:40 ` Eli Zaretskii
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=47C8A142-D5EE-49D0-8C91-CE2A28694D99@scratch.space \
--to=van@scratch.space \
--cc=32037@debbugs.gnu.org \
--cc=eliz@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).