From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <teawater@gmail.com>
Cc: brobecker@adacore.com, tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA] Set the default of disassemble-next-line to off
Date: Sun, 19 Apr 2009 17:43:00 -0000 [thread overview]
Message-ID: <83bpqsilpq.fsf@gnu.org> (raw)
In-Reply-To: <daef60380904190647o7b850a5fia60ffd3e9c493bfd@mail.gmail.com>
> Date: Sun, 19 Apr 2009 21:47:25 +0800
> From: Hui Zhu <teawater@gmail.com>
> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>
> 2009-04-19 Hui Zhu <teawater@gmail.com>
>
> * gdbint.texinfo (disassemble-next-line): Set the default of
> disassemble-next-line to off.
This is fine with me. Thanks.
next prev parent reply other threads:[~2009-04-19 17:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 13:47 Hui Zhu
2009-04-19 17:43 ` Eli Zaretskii [this message]
2009-04-20 16:30 ` Hui Zhu
2009-04-20 18:17 ` Tom Tromey
2009-04-22 6:42 ` Hui Zhu
2009-04-22 17:11 ` Eli Zaretskii
2009-04-22 18:46 ` Tom Tromey
2009-04-25 9:44 ` Eli Zaretskii
2009-04-23 3:46 ` Hui Zhu
2009-04-25 9:56 ` Eli Zaretskii
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=83bpqsilpq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=teawater@gmail.com \
--cc=tromey@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