Message ID | 1445507944-9197-7-git-send-email-palves@redhat.com |
---|---|
State | New, archived |
Headers |
Received: (qmail 37987 invoked by alias); 22 Oct 2015 09:59:16 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <gdb-patches.sourceware.org> List-Unsubscribe: <mailto:gdb-patches-unsubscribe-##L=##H@sourceware.org> List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org> List-Archive: <http://sourceware.org/ml/gdb-patches/> List-Post: <mailto:gdb-patches@sourceware.org> List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs> Sender: gdb-patches-owner@sourceware.org Delivered-To: mailing list gdb-patches@sourceware.org Received: (qmail 37896 invoked by uid 89); 22 Oct 2015 09:59:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL, BAYES_00, RP_MATCHES_RCVD, SPF_HELO_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 22 Oct 2015 09:59:13 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (Postfix) with ESMTPS id 4B100225 for <gdb-patches@sourceware.org>; Thu, 22 Oct 2015 09:59:12 +0000 (UTC) Received: from brno.lan (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t9M9x5Fx014526 for <gdb-patches@sourceware.org>; Thu, 22 Oct 2015 05:59:11 -0400 From: Pedro Alves <palves@redhat.com> To: gdb-patches@sourceware.org Subject: [PATCH 6/6] NEWS: "info" commands now list in ascending order Date: Thu, 22 Oct 2015 10:59:04 +0100 Message-Id: <1445507944-9197-7-git-send-email-palves@redhat.com> In-Reply-To: <1445507944-9197-1-git-send-email-palves@redhat.com> References: <1445507944-9197-1-git-send-email-palves@redhat.com> |
Commit Message
Pedro Alves
Oct. 22, 2015, 9:59 a.m. UTC
gdb/ChangeLog: 2015-10-22 Pedro Alves <palves@redhat.com> * NEWS: Mention that a few "info" commands now list the corresponding items in ascending order. --- gdb/NEWS | 4 ++++ 1 file changed, 4 insertions(+)
Comments
> From: Pedro Alves <palves@redhat.com> > Date: Thu, 22 Oct 2015 10:59:04 +0100 > > gdb/ChangeLog: > 2015-10-22 Pedro Alves <palves@redhat.com> > > * NEWS: Mention that a few "info" commands now list the > corresponding items in ascending order. > --- > gdb/NEWS | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/gdb/NEWS b/gdb/NEWS > index b2b1e99..e16e861 100644 > --- a/gdb/NEWS > +++ b/gdb/NEWS > @@ -24,6 +24,10 @@ > > * GDB now supports displaced stepping on AArch64 GNU/Linux. > > +* "info threads", "info inferiors", "info display", "info checkpoints" > + and "maint info program-spaces" now list the corresponding items in > + ascending order, for consistency with all other "info" commands. ^^ I'd suggest to add "alphabetic" where indicated. Otherwise, this is fine, thanks.
On 10/22/2015 04:00 PM, Eli Zaretskii wrote: >> From: Pedro Alves <palves@redhat.com> >> Date: Thu, 22 Oct 2015 10:59:04 +0100 >> >> gdb/ChangeLog: >> 2015-10-22 Pedro Alves <palves@redhat.com> >> >> * NEWS: Mention that a few "info" commands now list the >> corresponding items in ascending order. >> --- >> gdb/NEWS | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/gdb/NEWS b/gdb/NEWS >> index b2b1e99..e16e861 100644 >> --- a/gdb/NEWS >> +++ b/gdb/NEWS >> @@ -24,6 +24,10 @@ >> >> * GDB now supports displaced stepping on AArch64 GNU/Linux. >> >> +* "info threads", "info inferiors", "info display", "info checkpoints" >> + and "maint info program-spaces" now list the corresponding items in >> + ascending order, for consistency with all other "info" commands. > ^^ > I'd suggest to add "alphabetic" where indicated. That would sound very confusing to me, as we sort by e.g., thread ID, not thread name, and alphabetic would suggest to me that we now sort by "name" or whatever else looks like a name. Would "ascending ID order" or "ascending numerical order" instead be OK with you? > > Otherwise, this is fine, thanks. > Thanks, Pedro Alves
> Date: Thu, 22 Oct 2015 16:07:30 +0100 > From: Pedro Alves <palves@redhat.com> > CC: gdb-patches@sourceware.org > > > I'd suggest to add "alphabetic" where indicated. > > That would sound very confusing to me, as we sort by e.g., thread > ID, not thread name, and alphabetic would suggest to me that we > now sort by "name" or whatever else looks like a name. > > Would "ascending ID order" or "ascending numerical order" > instead be OK with you? Yes, of course. The point is just "ascending" doesn't say enough, we should say more about the order. (I mistakenly thought it was alphabetic.) Thanks.
diff --git a/gdb/NEWS b/gdb/NEWS index b2b1e99..e16e861 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -24,6 +24,10 @@ * GDB now supports displaced stepping on AArch64 GNU/Linux. +* "info threads", "info inferiors", "info display", "info checkpoints" + and "maint info program-spaces" now list the corresponding items in + ascending order, for consistency with all other "info" commands. + * New commands maint set target-non-stop (on|off|auto)