Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: [PUSHED OBV] The NEWS file had two "New targets" sections for 8.3.
Date: Tue, 12 Mar 2019 21:53:00 -0000	[thread overview]
Message-ID: <ed7e1c9a-cf00-0e50-8308-4ffac8cf587b@FreeBSD.org> (raw)
In-Reply-To: <ydd1s3byez4.fsf@CeBiTec.Uni-Bielefeld.DE>

On 3/12/19 2:12 PM, Rainer Orth wrote:
> John Baldwin <jhb@FreeBSD.org> writes:
> 
>> diff --git a/gdb/NEWS b/gdb/NEWS
>> index cc7c35c064..88ce9a7104 100644
>> --- a/gdb/NEWS
>> +++ b/gdb/NEWS
>> @@ -55,11 +55,6 @@
>>  * Removed support for old demangling styles arm, edg, gnu, hp and
>>    lucid.
>>  
>> -* New targets
>> -
>> -  NXP S12Z		s12z-*-elf
>> -  GNU/Linux/OpenRISC	or1k*-*-linux*
>> -
>>  * New commands
>>  
>>  set debug compile-cplus-types
>> @@ -187,6 +182,8 @@ GNU/Linux/RISC-V		riscv*-*-linux*
>>  CSKY ELF			csky*-*-elf
>>  CSKY GNU/LINUX			csky*-*-linux
>>  FreeBSD/riscv			riscv*-*-freebsd*
>> +NXP S12Z			s12z-*-elf
>> +GNU/Linux/OpenRISC		or1k*-*-linux*
> 
> Shouldn't they be sorted alphabetically, either by name or target
> triplet?

In the past few releases they've just been in "as-added" order.  Sorting
by some other thing seems fine to me, but I'll defer to the maintainers
on what key to use.

-- 
John Baldwin


      reply	other threads:[~2019-03-12 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 21:00 John Baldwin
2019-03-12 21:09 ` John Baldwin
2019-03-14  6:53   ` Joel Brobecker
2019-03-12 21:12 ` Rainer Orth
2019-03-12 21:53   ` John Baldwin [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=ed7e1c9a-cf00-0e50-8308-4ffac8cf587b@FreeBSD.org \
    --to=jhb@freebsd.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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