Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>, Anton Kolesov <Anton.Kolesov@synopsys.com>
Cc: gdb-patches@sourceware.org, Francois.Bedard@synopsys.com
Subject: Re: [PATCH v2] arc: New Synopsys ARC port
Date: Fri, 16 Sep 2016 18:33:00 -0000	[thread overview]
Message-ID: <2a09e4be-344b-b959-5be5-1c2519776f18@redhat.com> (raw)
In-Reply-To: <83r38j4rxf.fsf@gnu.org>

On 09/16/2016 07:31 PM, Eli Zaretskii wrote:

> (Should we have a NEWS entry?)
> 

You missed it:

On 09/16/2016 06:11 PM, Anton Kolesov wrote:
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 99e1013..37eed94 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -15,6 +15,10 @@
>    running on MS-Windows use to assign names to threads in the
>    debugger.
>  
> +* New targets
> +
> +Synopsys ARC			arc*-*-elf32
> +
>  *** Changes in GDB 7.12
>  
>  * GDB and GDBserver now build with a C++ compiler by default.

Thanks,
Pedro Alves


  reply	other threads:[~2016-09-16 18:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31  8:50 [PATCH 1/2] " Anton Kolesov
2016-08-31  8:50 ` [PATCH 2/2] Add myself as a write-after-approval GDB maintainer Anton Kolesov
2016-08-31 13:59 ` [PATCH 1/2] arc: New Synopsys ARC port Pedro Alves
2016-09-01 19:54   ` Anton Kolesov
2016-09-05 18:56     ` Pedro Alves
2016-09-15 11:39     ` Pedro Alves
2016-09-16 17:12       ` [PATCH v2] " Anton Kolesov
2016-09-16 17:54         ` Pedro Alves
2016-09-16 18:32         ` Eli Zaretskii
2016-09-16 18:33           ` Pedro Alves [this message]
2016-09-19 12:37             ` [PATCH v3] " Anton Kolesov
2016-09-19 17:02               ` Eli Zaretskii
2016-09-21 15:40                 ` [PATCH v4] " Anton Kolesov
2016-09-21 16:17                   ` Pedro Alves
2016-09-21 17:29                     ` Anton Kolesov
2016-09-21 17:30                       ` Pedro Alves

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=2a09e4be-344b-b959-5be5-1c2519776f18@redhat.com \
    --to=palves@redhat.com \
    --cc=Anton.Kolesov@synopsys.com \
    --cc=Francois.Bedard@synopsys.com \
    --cc=eliz@gnu.org \
    --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