From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: MI/CLI breakpoint handling code duplication
Date: Fri, 14 Dec 2007 17:06:00 -0000 [thread overview]
Message-ID: <20071214140748.GA14688@caradoc.them.org> (raw)
In-Reply-To: <200712140926.49689.ghost@cs.msu.su>
On Fri, Dec 14, 2007 at 10:26:49AM +0400, Vladimir Prus wrote:
> Ping? This patch is pure refactoring which is basis for
> the 'pending breakpoint in MI' patch. Given that the patch
> is not supposed to change any behaviour and causes no regression,
> I'd hope it should be easy to review :-)
>
> I reattach the patch in case the original email is already lost.
OK.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-12-14 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 10:26 Vladimir Prus
2007-12-14 14:08 ` Vladimir Prus
2007-12-14 17:06 ` Daniel Jacobowitz [this message]
2008-01-11 22:03 Nick Roberts
2008-01-11 22:05 Nick Roberts
2008-01-15 20:43 ` Vladimir Prus
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=20071214140748.GA14688@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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