Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: "J. Johnston" <jjohnstn@redhat.com>
Cc: Eli Zaretskii <eliz@elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [RFC]: pending break support
Date: Fri, 05 Dec 2003 03:44:00 -0000	[thread overview]
Message-ID: <20031205034451.GA13705@nevyn.them.org> (raw)
In-Reply-To: <3FCF6724.5050109@redhat.com>

On Thu, Dec 04, 2003 at 11:56:04AM -0500, J. Johnston wrote:
> 
> 
> Eli Zaretskii wrote:
> >>Date: Wed, 03 Dec 2003 14:46:49 -0500
> >>From: "J. Johnston" <jjohnstn@redhat.com>

> >>+Normal breakpoint operations apply to pending breakpoints as well.  You 
> >>may +specify, a condition for a pending breakpoint, commands to run when 
> >>the 
> >
> >          ^
> >The comma I marked should not be there, I think.
> >
> 
> I put the comma because you can specify a condition and you can specify 
> commands.  Without it, the next part of the sentence doesn't make sense.  I 
> didn't want to reuse specify as that made the sentence feel redundant.  I 
> think maybe the best idea would be to use "or" instead of the commas.
> 
> How about:
> 
> Normal breakpoint operations apply to pending breakpoints as well.  You may 
> specify a condition for a pending breakpoint and/or commands to run when 
> the breakpoint is reached.  You can also enable or disable the pending 
> breakpoint.
> ...

Normally English doesn't go in for commas before lists.  But your
rewrite reads well to me.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-12-05  3:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03  1:35 J. Johnston
2003-12-03 16:06 ` Eli Zaretskii
2003-12-03 19:46   ` J. Johnston
2003-12-04  8:30     ` Eli Zaretskii
2003-12-04 16:56       ` J. Johnston
2003-12-05  3:44         ` Daniel Jacobowitz [this message]
2003-12-05 16:09         ` Eli Zaretskii
2003-12-05  4:56 ` Daniel Jacobowitz
2003-12-10 22:17 ` Tom Tromey

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=20031205034451.GA13705@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=eliz@elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@redhat.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