From: Eli Zaretskii <eliz@gnu.org>
To: Matt Rice <ratmice@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch][python][doc] PR 12918 reference decode_line in py SAL docs.
Date: Sun, 03 Jul 2011 02:58:00 -0000 [thread overview]
Message-ID: <838vsgqdd0.fsf@gnu.org> (raw)
In-Reply-To: <CACTLOFqhd4NJshLF9rpSToMLhDy43QsdU0s9+XVuodk_zZOXhw@mail.gmail.com>
> Date: Sat, 2 Jul 2011 14:53:42 -0700
> From: Matt Rice <ratmice@gmail.com>
> Cc: gdb-patches@sourceware.org
>
> Thus my hope was that a complete chain of links from the goal, would
> provoke a more keen investigation into existing docs.
>
> If someone has a better idea for further clarifying it i'm all for it.
Maybe we should simply ask the OP what, if anything, is missing, given
the existing documentation of decode_line.
prev parent reply other threads:[~2011-07-03 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 14:20 Matt Rice
2011-07-02 17:00 ` Eli Zaretskii
2011-07-02 21:54 ` Matt Rice
2011-07-03 2:58 ` Eli Zaretskii [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=838vsgqdd0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ratmice@gmail.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