From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [2/2] RFC: let "commands" affect multiple breakpoints
Date: Tue, 23 Mar 2010 17:24:00 -0000 [thread overview]
Message-ID: <83k4t3gdcv.fsf@gnu.org> (raw)
In-Reply-To: <m3bpefpsxu.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Mon, 22 Mar 2010 22:23:25 -0600
>
> 2010-03-12 Tom Tromey <tromey@redhat.com>
>
> PR breakpoints/9352:
> * NEWS: Mention changes to `commands' and `rbreak'.
>
> 2010-03-12 Tom Tromey <tromey@redhat.com>
>
> PR breakpoints/9352:
> * gdb.texinfo (Break Commands): Update.
These two parts are okay. Thanks.
next prev parent reply other threads:[~2010-03-23 17:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 3:54 Tom Tromey
2010-03-10 16:34 ` Tom Tromey
2010-03-10 17:05 ` Pedro Alves
2010-03-11 21:42 ` Tom Tromey
2010-03-23 4:23 ` Tom Tromey
2010-03-23 17:24 ` Eli Zaretskii [this message]
2010-03-24 21:21 ` Tom Tromey
2010-03-25 17:09 ` Pedro Alves
2010-03-30 20:42 ` Tom Tromey
2010-04-01 11:47 ` Pedro Alves
2010-04-01 13:32 ` Eli Zaretskii
2010-03-10 17:37 ` Eli Zaretskii
2010-03-11 20:50 ` Tom Tromey
2010-03-12 7:53 ` 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=83k4t3gdcv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@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