Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: nickrob@snap.net.nz (Nick Roberts)
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] GDB/MI documentation
Date: Thu, 14 May 2009 22:07:00 -0000	[thread overview]
Message-ID: <18956.38423.255406.48556@totara.tehura.co.nz> (raw)
In-Reply-To: <guhcv3$gih$1@ger.gmane.org>

Vladimir Prus writes:
 > Nick Roberts wrote:
 > 
 > > - Notifications is the mechanism for reporting changes in the state of the
 > > - target,
 > > 
 > > + Notifications are used for reporting changes in the state of the
 > > + target,
 > > 
 > > It's generally considered bad English to use "is" after a plural word.
 > 
 > Unfortunately, you have made a semantic change to the sentence. Original
 > sentence was definition what notification is. The changed sentence, instead,
 > say what notifications do, and is not a definition.

You've defined them by what they do, so the definition here is implicit.  If
you want to emphasise the definition, you could use @dfn{}.  In any case,
in the patch I've committed, I've not changed this.

After describing them in the node, GDB/MI General Design, the documentation
uses older terminolgy and they are generally referred to as async records.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2009-05-14 22:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 10:36 Nick Roberts
2009-05-13 11:59 ` Vladimir Prus
2009-05-13 18:03   ` Eli Zaretskii
2009-05-13 18:05 ` Eli Zaretskii
2009-05-14  6:51   ` Nick Roberts
2009-05-14 15:22     ` Vladimir Prus
2009-05-14 22:07       ` Nick Roberts [this message]
2009-05-14 19:02     ` Eli Zaretskii
2009-05-14 21:50       ` Nick Roberts
2009-05-15  7:00         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18956.38423.255406.48556@totara.tehura.co.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.com \
    /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