public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Eric Botcazou <ebotcazou@adacore.com>,
	       James Bowman <james.bowman@ftdichip.com>
Cc: gcc-patches@gcc.gnu.org,
	Segher Boessenkool <segher@kernel.crashing.org>,
	       Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH, FT32] initial support
Date: Wed, 03 Jun 2015 13:56:00 -0000	[thread overview]
Message-ID: <556F03AA.9020508@redhat.com> (raw)
In-Reply-To: <2025621.TthFiZvRWe@polaris>

On 05/28/2015 03:50 PM, Eric Botcazou wrote:
>> Thanks very much. ChangeLog entry:
>>
>> 2015-05-14  James Bowman  <james.bowman@ftdichip.com>
>>
>>          * configure.ac: FT32 target added
>>          * libgcc/config.host: FT32 target added
>>          * gcc/config/ft32/: FT32 target added
>>          * libgcc/config/ft32/: FT32 target added
>>          * gcc/doc/install.texi, invoke.texi, md.texi: FT32 details added
>>          * gcc/doc/contrib.texi: self added
>>          * contrib/config-list.mk: FT32 target added
>>          * configure: Regenerated
>
> That's wrong, you cannot add just a single entry to the toplevel ChangeLog,
> you need to add entries to the ChangeLog of every subdirectory instead: gcc,
> libgcc, contrib, etc.  Please fix.
Done.
jeff

  reply	other threads:[~2015-06-03 13:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03  5:18 James Bowman
2015-02-03  6:05 ` Andrew Pinski
2015-02-03 14:44   ` Paolo Bonzini
2015-02-04  2:26     ` James Bowman
2015-02-03 22:51 ` Joseph Myers
2015-02-11  3:42   ` James Bowman
2015-02-11 17:04     ` Joseph Myers
2015-02-11 23:58       ` James Bowman
2015-02-12 12:39         ` Joseph Myers
2015-02-16 10:00       ` James Bowman
2015-02-16 18:07         ` Joseph Myers
2015-02-16 22:36           ` James Bowman
2015-03-10 15:49           ` James Bowman
2015-03-19 15:29           ` James Bowman
2015-04-29  7:41             ` Jeff Law
     [not found]               ` <CA9BBF0458F83C4F9051448B941B57D117B98521@glaexch3>
2015-05-11 20:35                 ` Jeff Law
2015-05-12 22:36                   ` James Bowman
2015-05-12 22:54                     ` Jeff Law
2015-05-12 23:10                       ` Mike Stump
2015-05-13  1:07                     ` Segher Boessenkool
2015-05-14  1:58                       ` James Bowman
2015-05-14 11:40                         ` Segher Boessenkool
2015-05-14 12:58                         ` Segher Boessenkool
2015-05-14 13:11                           ` Segher Boessenkool
2015-05-14 15:30                             ` James Bowman
2015-05-14 17:42                               ` Segher Boessenkool
2015-05-14 18:48                                 ` Jeff Law
2015-05-14 19:51                                   ` Segher Boessenkool
2015-05-14 20:06                                     ` Jeff Law
2015-05-15  3:01                                       ` James Bowman
2015-05-15  6:41                                         ` Jeff Law
2015-05-28 22:35                                         ` Eric Botcazou
2015-06-03 13:56                                           ` Jeff Law [this message]
2015-05-14 18:31                               ` Jeff Law

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=556F03AA.9020508@redhat.com \
    --to=law@redhat.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=james.bowman@ftdichip.com \
    --cc=joseph@codesourcery.com \
    --cc=segher@kernel.crashing.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).