From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Check original contents at tracepoints
Date: Sat, 24 Apr 2010 06:32:00 -0000 [thread overview]
Message-ID: <83vdbh1hvy.fsf@gnu.org> (raw)
In-Reply-To: <4BD24BC1.4030103@codesourcery.com>
> Date: Fri, 23 Apr 2010 18:39:13 -0700
> From: Stan Shebs <stan@codesourcery.com>
>
> So before getting mired in still more idiosyncrasy, it seems like a good
> idea to check whether this is of interest for FSF GDB, and to get ideas
> on how to handle it.
If the idea and the code are accepted, the patch for the manual is
fine with me.
next prev parent reply other threads:[~2010-04-24 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 1:39 Stan Shebs
2010-04-24 6:32 ` Eli Zaretskii [this message]
2010-05-27 19:45 ` 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=83vdbh1hvy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stan@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