From: Roland Schwingel <email@example.com>
Subject: Re: [PATCH/gdbtk] Update stackwin gdb api usage
Date: Fri, 25 May 2012 10:23:00 -0000 [thread overview]
Message-ID: <4FBF5D78.firstname.lastname@example.org> (raw)
Thanks for reviewing Keith!
I applied this now with all your comments taken into account.
Some of the formatting things had also been on my side not only
on your email clients side. Sorry for that!
ATTENTION: At present insight is not compiling!
This is not reasoned by my patch but due to changes inside of
gdb itself. I will formulate a (trivial) patch for that.
next reply other threads:[~2012-05-25 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 10:23 Roland Schwingel [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-02 15:21 Roland Schwingel
2012-05-24 1:12 ` Keith Seitz
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).