From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@redhat.com>,
palves@redhat.com, brobecker@adacore.com,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Display configuration details in --help
Date: Sun, 14 Apr 2013 14:16:00 -0000 [thread overview]
Message-ID: <20840.16822.376163.822626@ruffy2.mtv.corp.google.com> (raw)
In-Reply-To: <83eheg9lbr.fsf@gnu.org>
Eli Zaretskii writes:
> > From: Tom Tromey <tromey@redhat.com>
> > Cc: Doug Evans <dje@google.com>, Eli Zaretskii <eliz@gnu.org>,
> > Joel Brobecker <brobecker@adacore.com>,
> > gdb-patches <gdb-patches@sourceware.org>
> > Date: Wed, 10 Apr 2013 13:16:39 -0600
> >
> > Pedro> But we shouldn't stale Eli's patch for this.
> >
> > Yes, I agree.
>
> Thanks, committed.
>
> I will take a shot on regrouping the --help text later.
Hi. It helps my browsing of ChangeLog entries if they follow
the convention that related patches are not separated by a blank line.
Plus I added an entry for NEWS.
Committed.
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.15404
diff -u -p -r1.15404 ChangeLog
--- ChangeLog 12 Apr 2013 16:04:07 -0000 1.15404
+++ ChangeLog 12 Apr 2013 17:11:23 -0000
@@ -91,13 +91,12 @@
2013-04-12 Eli Zaretskii <eliz@gnu.org>
+ * NEWS: Mention "show configuration", --configuration.
* top.c (print_gdb_configuration): New function, displays the
details about GDB configure-time parameters.
(print_gdb_version): Mention "show configuration".
-
* cli/cli-cmds.c (show_configuration): New function.
(_initialize_cli_cmds): Add the "show configuration" command.
-
* main.c (captured_main) <print_configuration>: New static var.
<long_options>: Use it.
If --configuration was given, call print_gdb_configuration.
next prev parent reply other threads:[~2013-04-12 17:17 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 17:46 Eli Zaretskii
2013-03-21 18:00 ` Doug Evans
2013-03-21 18:25 ` Pedro Alves
2013-03-21 18:29 ` Joel Brobecker
2013-03-21 18:44 ` Eli Zaretskii
2013-03-21 19:11 ` Joel Brobecker
2013-03-21 20:39 ` Eli Zaretskii
2013-03-21 20:55 ` Joel Brobecker
2013-03-21 21:17 ` Tom Tromey
2013-03-21 22:23 ` Eli Zaretskii
2013-04-09 19:31 ` Eli Zaretskii
2013-04-09 19:46 ` Doug Evans
2013-04-09 20:04 ` Eli Zaretskii
2013-04-09 23:33 ` Doug Evans
2013-04-10 0:12 ` Pedro Alves
2013-04-10 0:48 ` Eli Zaretskii
2013-04-10 2:51 ` Doug Evans
2013-04-10 4:41 ` Eli Zaretskii
2013-04-11 2:41 ` Doug Evans
2013-04-11 1:20 ` Tom Tromey
2013-04-11 1:24 ` Pedro Alves
2013-04-11 2:43 ` Tom Tromey
2013-04-12 12:50 ` Eli Zaretskii
2013-04-12 14:43 ` Eli Zaretskii
2013-04-12 16:39 ` regroup --help text (was: Re: [PATCH] Display configuration details in --help) Pedro Alves
2013-06-22 11:31 ` regroup --help text " Eli Zaretskii
2013-06-25 19:30 ` Pedro Alves
2013-07-06 7:35 ` Eli Zaretskii
2013-04-12 20:50 ` [PATCH] Display configuration details in --help Tom Tromey
2013-04-14 14:17 ` Joel Brobecker
2013-04-16 1:34 ` Doug Evans
2013-04-16 9:46 ` regroup --help text Eli Zaretskii
2013-04-17 8:10 ` Doug Evans
2013-04-17 12:28 ` Eli Zaretskii
2013-04-14 14:16 ` Doug Evans [this message]
2013-04-10 0:38 ` [PATCH] Display configuration details in --help Eli Zaretskii
2013-04-10 3:06 ` Doug Evans
2013-04-10 4:44 ` Eli Zaretskii
2013-03-21 18:53 ` 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=20840.16822.376163.822626@ruffy2.mtv.corp.google.com \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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