From: Eli Zaretskii <eliz@gnu.org>
To: Chris Genly <chgenly@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: MI: -var-list-children doc error
Date: Wed, 17 Jun 2009 17:41:00 -0000 [thread overview]
Message-ID: <E1MGz8O-0000ig-2A@fencepost.gnu.org> (raw)
In-Reply-To: <ed4903890906171032u60b52ec4g60204748c2b6ef98@mail.gmail.com> (message from Chris Genly on Wed, 17 Jun 2009 10:32:44 -0700)
> Date: Wed, 17 Jun 2009 10:32:44 -0700
> From: Chris Genly <chgenly@gmail.com>
> Cc: gdb@sourceware.org
>
> I can do that. Please direct me to the right files and let me know what formats.
The GDB manual's source is gdb/doc/gdb.texinfo. It's written in
Texinfo, but is almost pure text, so I think producing a patch will
not be difficult, even if you are not familiar with Texinfo. (If you
want to learn about Texinfo, typing "info texinfo" at your shell
prompt will most probably show you the Texinfo manual.)
Please post the patches to gdb-patches@sourceware.org.
Thanks.
prev parent reply other threads:[~2009-06-17 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 17:14 Chris Genly
2009-06-17 17:29 ` Eli Zaretskii
2009-06-17 17:32 ` Chris Genly
2009-06-17 17:41 ` 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=E1MGz8O-0000ig-2A@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=chgenly@gmail.com \
--cc=gdb@sourceware.org \
/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