Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: don.lee@sunplusct.com
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Support new target S+core 3, a variant of S+core
Date: Fri, 20 Mar 2009 15:02:00 -0000	[thread overview]
Message-ID: <uwsakpiiq.fsf@gnu.org> (raw)
In-Reply-To: <OF93CD693B.168FEC6A-ON4825757F.000C66C2-4825757F.000D0358@sunplusct.com>

> Cc: brobecker@adacore.com, gdb-patches@sourceware.org
> From: don.lee@sunplusct.com
> Date: Fri, 20 Mar 2009 10:20:36 +0800
> 
> Attachment is the patch for gdb/NEWS, says we add a new target, S+core 3,
> a variant of S+core.
> 
> Thank you for your time,
> Don
> 
> ChangLog entry:
> 2009-03-20      Don Lee <don.lee@sunplusct.com>:
> 
>         * gdb/NEWS: support new target, S+core 3

Thanks.

> --- src/gdb/NEWS	2009-02-18 01:56:50.000000000 +0800
> +++ src.mod/gdb/NEWS	2009-03-20 10:15:53.000000000 +0800
> @@ -209,6 +209,7 @@
>  
>  x86 DICOS			i[34567]86-*-dicos*
>  x86_64 DICOS		        x86_64-*-dicos*
> +S+core 3            score-elf

Please align the "score-elf" part with the preceding lines.  (I'm
guessing that you are using an editor that displays a TAB as 4-column
wide whitespace.)

Also, I wonder if it would make sense to include with the NEWS entry a
URL for where one could find a description of platforms that are not
widely know/used.  (DICOS could use such a URL as well, but at least I
was able to find its description in a matter of seconds by googling
for ``DICOS operating system''; no such luck for ``S+core 3'',
whatever that is.)  I realize that we have never asked for this in
previous NEWS entries, but looking now at past entries, I see that
they are all either sufficiently known or their names are spelled out
in sufficient detail that googling for them yields instantaneous hits.


  reply	other threads:[~2009-03-20 10:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17  2:17 don.lee
2009-03-17 16:12 ` Joel Brobecker
2009-03-19  7:36   ` don.lee
2009-03-19 13:59     ` Joel Brobecker
2009-03-20  2:37     ` Eli Zaretskii
2009-03-20 10:59       ` don.lee
2009-03-20 15:02         ` Eli Zaretskii [this message]
     [not found]       ` <OF51713D49.22E58C13-ON4825757F.00065D83-4825757F.000703CE@sunplusct.com>
2009-03-24 20:33         ` Joel Brobecker
     [not found]           ` <OF8D1ED069.1AB0D24B-ON48257586.0008306A-48257586.000B6BC2@sunplusct.com>
2009-03-30 15:17             ` Joel Brobecker
     [not found] <OFDAF6A5BC.66B4412D-ON48257582.00087E06-48257582.00096DDA@sunplusct.com>
2009-03-23  4:28 ` 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=uwsakpiiq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=don.lee@sunplusct.com \
    --cc=gdb-patches@sourceware.org \
    /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