From: Laszlo Ersek <lersek@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] docs: describe the QEMU build system structure / design
Date: Tue, 22 Sep 2015 20:28:09 +0200 [thread overview]
Message-ID: <56019DB9.3020804@redhat.com> (raw)
In-Reply-To: <560199E7.6020401@redhat.com>
meta review of your review:
On 09/22/15 20:11, John Snow wrote:
> Reviewed from an en_US perspective, though I left alone things that are
> clearly regional (e.g. 'behaviour' vs 'behavior')
>
> On 09/22/2015 12:35 PM, Daniel P. Berrange wrote:
>> + - Add information to the help output message to report on the new
>> + feature flag.
>> +
>
> Remove period, or add to the other list items for consistency. My
> personal preference is to use the period for any sentences with proper
> grammatical structure, omitting it for simple list items.
Then:
>> +which create binaries must include the $(EXESUF) variable on the binary
>> +name. eg
>
> 'e.g.' here and everywhere subsequent.
Self-contradiction found!!!1111eleven
:)
Honestly I'm surprised (or not) how many typos you've found that I
blissfully slid over.
>> +Each system/userspace emulation target needs to have a slightly
>> +different set of make rules / variables. Thus, make will be recursively
>> +invoked for each of the emulation targets.
>> +
>> +The recursive invokation will end up processing the toplevel
>
> invocation again.
Self-contradictory period again! :)
> Thanks for writing this!
Yes!
> Pretending to be Eric,
Yes. :)
Cheers
Laszlo
next prev parent reply other threads:[~2015-09-22 18:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 16:35 [Qemu-devel] [PATCH] docs: describe the QEMU build system structure / design Daniel P. Berrange
2015-09-22 18:11 ` John Snow
2015-09-22 18:28 ` Laszlo Ersek [this message]
2015-09-22 18:51 ` Eric Blake
2015-09-22 19:01 ` Laszlo Ersek
2015-09-22 19:47 ` Paolo Bonzini
2015-09-22 18:21 ` Laszlo Ersek
2015-09-22 18:22 ` Eric Blake
2015-09-23 8:35 ` Daniel P. Berrange
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=56019DB9.3020804@redhat.com \
--to=lersek@redhat.com \
--cc=jsnow@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 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.