From: John Darrington <john@darrington.wattle.id.au>
To: git@vger.kernel.org
Subject: Awkward and confusing question in git --send-email
Date: Sat, 23 Apr 2016 20:22:35 +0200 [thread overview]
Message-ID: <20160423182235.GA20615@jocasta.intra> (raw)
[-- Attachment #1: Type: text/plain, Size: 523 bytes --]
Git --send-email poses the question:
"Who should the emails be sent to (if any)?"
Apart from sounding clumsy (not to mention incorrect grammar), it took me a while to work out what this meant.
I suggest this be changed to :
"To whom should the email be sent (if anyone) ?"
J'
--
Avoid eavesdropping. Send strong encryted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2016-04-23 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 18:22 John Darrington [this message]
2016-04-24 19:31 ` Awkward and confusing question in git --send-email Junio C Hamano
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=20160423182235.GA20615@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).