From: Tom Tromey <tromey@redhat.com>
To: Daniel Colascione <daniel@censorshipresearch.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Less verbose Python commands
Date: Mon, 11 Jan 2010 21:32:00 -0000 [thread overview]
Message-ID: <m3pr5gnx9x.fsf@fleche.redhat.com> (raw)
In-Reply-To: <hic27v$365$1@ger.gmane.org> (Daniel Colascione's message of "Sun, 10 Jan 2010 03:13:52 -0500")
>>>>> "Daniel" == Daniel Colascione <daniel@censorshipresearch.org> writes:
Daniel> Err, this version propagates docstrings to command help too:
Nice.
Do you have an assignment on file? If not, email me and I can get you
started on that.
To put this in we'd need to merge in the code to add a Python library to
gdb. We'll have to do this eventually though...
Tom
prev parent reply other threads:[~2010-01-11 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 8:05 Daniel Colascione
2010-01-10 8:14 ` Daniel Colascione
2010-01-11 21:32 ` Tom Tromey [this message]
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=m3pr5gnx9x.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=daniel@censorshipresearch.org \
--cc=gdb-patches@sources.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