From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: [commit] [doc patch] Fix '.debug_gdb_scripts section' node name for info
Date: Tue, 27 Mar 2012 20:16:00 -0000 [thread overview]
Message-ID: <20120327201618.GA24630@host2.jankratochvil.net> (raw)
In-Reply-To: <E1SCcjd-0001LT-VV@fencepost.gnu.org>
On Tue, 27 Mar 2012 22:11:17 +0200, Eli Zaretskii wrote:
> > Date: Tue, 27 Mar 2012 21:19:03 +0200
> > From: Jan Kratochvil <jan.kratochvil@redhat.com>
> >
> > if you try to jump into the link '.debug_gdb_scripts section' or even just
> > 'n'/'p' navigate around that node you will find it does not work (at least not
> > in info-4.13a-16.fc17.x86_64).
> >
> > OK this way or should there be some more name vs. node aliases in the
> > refeerences?
>
> This is OK, thanks.
Checked in:
http://sourceware.org/ml/gdb-cvs/2012-03/msg00296.html
Thanks,
Jan
prev parent reply other threads:[~2012-03-27 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 19:19 Jan Kratochvil
2012-03-27 20:11 ` Eli Zaretskii
2012-03-27 20:16 ` Jan Kratochvil [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=20120327201618.GA24630@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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