From: "Mike D. Day" <ncmike@ncultra.org>
To: Brad Hards <bradh@frogmouth.net>
Cc: Llu??s Vilanova <vilanova@ac.upc.edu>,
qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Llu??s <xscript@gmx.net>
Subject: Re: [Qemu-devel] docs/tracing.txt: minor documentation fixes
Date: Tue, 26 Apr 2011 17:00:50 -0400 [thread overview]
Message-ID: <20110426210050.GA79148@shoshone.local> (raw)
In-Reply-To: <201104270646.52693.bradh@frogmouth.net>
On 27/04/11 06:46 +1000, Brad Hards wrote:
> On Tue, 26 Apr 2011 10:26:01 pm Stefan Hajnoczi wrote:
> > -There is a set of static trace events declared in the trace-events source
> > +There is a set of static trace events declared in the "trace-events"
> > source
> Would it read better if it said "There are a set..." (i.e. "are" instead of
> "is")?
I belive it's correct: there is a set. The alternative would be "there
are static trace events."
Mike
--
Mike Day | ultra@ncultra.org | "Endurance is a Virtue"
next prev parent reply other threads:[~2011-04-26 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 12:25 [Qemu-devel] [PULL 0/6] Tracing patches Stefan Hajnoczi
2011-04-26 12:25 ` [Qemu-devel] [PATCH 1/6] tracetool: allow ) in trace output string Stefan Hajnoczi
2011-04-26 12:25 ` [Qemu-devel] [PATCH 2/6] trace: Remove %s in grlib trace events Stefan Hajnoczi
2011-04-26 12:26 ` [Qemu-devel] [PATCH 3/6] docs: Trace events must not expect pointer dereferencing Stefan Hajnoczi
2011-04-26 12:26 ` [Qemu-devel] [PATCH 4/6] docs/tracing.txt: minor documentation fixes Stefan Hajnoczi
2011-04-26 20:46 ` Brad Hards
2011-04-26 21:00 ` Mike D. Day [this message]
2011-04-26 12:26 ` [Qemu-devel] [PATCH 5/6] trace: [ust] fix generation of 'trace.c' on events without args Stefan Hajnoczi
2011-04-26 12:26 ` [Qemu-devel] [PATCH 6/6] trace: [trace-events] fix print formats in some events Stefan Hajnoczi
2011-04-26 13:19 ` [Qemu-devel] [PULL 0/6] Tracing patches Anthony Liguori
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=20110426210050.GA79148@shoshone.local \
--to=ncmike@ncultra.org \
--cc=bradh@frogmouth.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=vilanova@ac.upc.edu \
--cc=xscript@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.
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).