public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ian Lance Taylor via gcc-patches" <gcc-patches@gcc.gnu.org>
To: James Cowgill <James.Cowgill@imgtec.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] go.test: update MIPS architecture names
Date: Fri, 23 Jun 2017 13:19:00 -0000	[thread overview]
Message-ID: <CAKOQZ8wMvszQQhqtrxmMK8yo-qMp+n5wJ6esrFk3+v9wAwuNeQ@mail.gmail.com> (raw)
In-Reply-To: <fdb028c5-f508-8889-2170-81f9732ae30e@imgtec.com>

On Fri, Jun 23, 2017 at 5:40 AM, James Cowgill <James.Cowgill@imgtec.com> wrote:
>
> This updates the go architecture names on MIPS in line with the recent
> changes to libgo.
>
> I do not have commit access, so please can someone else commit this for
> me.
>
> Thanks,
> James
>
> 2016-06-23  James Cowgill  <James.Cowgill@imgtec.com>
>
>         * go.test/go-test.exp (go-set-goarch): update MIPS architecture
>         names.

Thanks.  Committed.

Ian

      reply	other threads:[~2017-06-23 13:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 12:40 James Cowgill
2017-06-23 13:19 ` Ian Lance Taylor via gcc-patches [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=CAKOQZ8wMvszQQhqtrxmMK8yo-qMp+n5wJ6esrFk3+v9wAwuNeQ@mail.gmail.com \
    --to=gcc-patches@gcc.gnu.org \
    --cc=James.Cowgill@imgtec.com \
    --cc=iant@google.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).