From: Tom Tromey <tromey@redhat.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: Vladimir Prus <vladimir@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [MI tracepoints 2/9] unify breakpoint commands and tracepoint actions
Date: Mon, 15 Mar 2010 21:00:00 -0000 [thread overview]
Message-ID: <m34okhe1wx.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4B9E72C5.60303@codesourcery.com> (Stan Shebs's message of "Mon, 15 Mar 2010 10:47:49 -0700")
>>>>> "Stan" == Stan Shebs <stan@codesourcery.com> writes:
Stan> OK with those additions. Tom, is this going to interfere with your
Stan> multiple-breakpoints commands patch? Should we do any coordination on
Stan> that?
They will probably conflict, but that is ok.
I will just wait and rebase my patch after this one goes in.
Tom
next prev parent reply other threads:[~2010-03-15 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 8:47 Vladimir Prus
2010-03-15 17:48 ` Stan Shebs
2010-03-15 21:00 ` Tom Tromey [this message]
2010-03-16 11:38 ` Vladimir Prus
2010-03-22 15:01 ` Stan Shebs
2010-03-23 21:37 ` Vladimir Prus
2010-03-16 0:56 ` Pedro Alves
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=m34okhe1wx.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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