From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] rename "set debugvarobj" to "set debug varobj"
Date: Tue, 29 Apr 2014 17:58:00 -0000 [thread overview]
Message-ID: <20140429175844.GE4420@adacore.com> (raw)
In-Reply-To: <1398785790-2059-1-git-send-email-tromey@redhat.com>
> I chose not to install deprecated aliases, since this is only a debug
> setting; but if someone feels strongly about it I will add them.
FWIW, that seems fine to me.
> 2014-04-29 Tom Tromey <tromey@redhat.com>
>
> * varobj.c (_initialize_varobj): Rename to "set debug varobj" and
> "show debug varobj".
>
> 2014-04-29 Tom Tromey <tromey@redhat.com>
>
> * gdb.texinfo (Debugging Output): Rename to "set debug varobj" and
> "show debug varobj".
Thanks for doing that, Tom!
--
Joel
next prev parent reply other threads:[~2014-04-29 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 15:36 Tom Tromey
2014-04-29 16:10 ` Eli Zaretskii
2014-04-29 17:58 ` Joel Brobecker [this message]
2014-04-30 13:18 ` Andrew Burgess
2014-05-08 14:35 ` Tom Tromey
2014-05-08 14:37 ` Tom Tromey
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=20140429175844.GE4420@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).