public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Oleg Endo <oleg.endo@t-online.de>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [SH][committed] Remove SH5 support in compiler
Date: Sat, 30 Apr 2016 11:02:00 -0000	[thread overview]
Message-ID: <1462014163.31604.77.camel@t-online.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1604300936120.12556@digraph.polyomino.org.uk>

Joseph,

Thanks for keeping an eye on that.

On Sat, 2016-04-30 at 09:39 +0000, Joseph Myers wrote:
> On Sat, 30 Apr 2016, Oleg Endo wrote:
> 
> > 	* config.guess:  Remove SH5 support.
> > 	* config.sub: Likewise.
> 
> Please revert.  These files must come verbatim from config.git with 
> no local changes.  If you persuade config-patches that SH5 support
> should be removed there then you can import new, unmodified upstream
> files.

Done (r235677).  I've sent the patch to config-patches.

> 
> > 	* configure: Likewise.
> 
> For all the configure scripts listed, regeneration rather than manual
> editing is appropriate.  Please make sure the changes you committed 
> are identical to those from a proper regeneration with the right 
> autoconf version.

Did that.  Looks there are no changes after regeneration.

Cheers,
Oleg

  reply	other threads:[~2016-04-30 11:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28  1:27 Oleg Endo
2016-04-29 10:45 ` Oleg Endo
2016-04-29 14:11   ` Oleg Endo
2016-04-30  1:58     ` Oleg Endo
2016-04-30  5:44       ` Oleg Endo
2016-04-30  9:22         ` Oleg Endo
2016-04-30  9:39           ` Joseph Myers
2016-04-30 11:02             ` Oleg Endo [this message]
2016-05-03 22:42               ` Eric Botcazou
2016-05-11 12:37                 ` Oleg Endo

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=1462014163.31604.77.camel@t-online.de \
    --to=oleg.endo@t-online.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    /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).