From: Eric Blake <eblake@redhat.com>
To: John Snow <jsnow@redhat.com>, Laszlo Ersek <lersek@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] docs: describe the QEMU build system structure / design
Date: Wed, 23 Sep 2015 10:47:48 -0600 [thread overview]
Message-ID: <5602D7B4.5060504@redhat.com> (raw)
In-Reply-To: <5602CAC0.20709@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
On 09/23/2015 09:52 AM, John Snow wrote:
>>> +Windows platform portability
>>> +----------------------------
>>> +
>>> +On Windows all binaries have a 'exe' suffix, so all the Makefile rules
>>
>> This was
>>
>> "a .exe suffix"
>>
>> before, and Jon commented that you probably pronounced it as "a dot-exe
>> suffix".
>>
>> Now you've removed the dot, but haven't changed "a" into "an". :)
>>
>
> Ah, I didn't realize he changed this -- I wasn't actually recommending
> that you change it, it was supposed to just be an observation.
>
> "a .exe" or "an exe" are both correct in my mind and you can use
> whichever you find reads easiest.
Actually, the full suffix is the four bytes '.exe', when compared to the
non-windows binaries. So I'd rather see:
On Windows, all binaries have the suffix ".exe", so all Makefile...
(note how I cleverly avoided the need for an indefinite article)
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2015-09-23 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 9:59 [Qemu-devel] [PATCH v2] docs: describe the QEMU build system structure / design Daniel P. Berrange
2015-09-23 10:06 ` Paolo Bonzini
2015-09-23 15:13 ` John Snow
2015-09-23 15:46 ` Laszlo Ersek
2015-09-23 15:47 ` Laszlo Ersek
2015-09-23 15:52 ` John Snow
2015-09-23 16:47 ` Eric Blake [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5602D7B4.5060504@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).