From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: thomas@codesourcery.com (Thomas Schwinge)
Cc: gcc-patches@gcc.gnu.org, dje.gcc@gmail.com
Subject: Re: [RFA][1/3] Remove Cell Broadband Engine SPU targets
Date: Tue, 08 Oct 2019 16:29:00 -0000 [thread overview]
Message-ID: <20191008162902.97505D802F5@oc3748833570.ibm.com> (raw)
In-Reply-To: <875zkz1qbd.fsf@euler.schwinge.homeip.net> from "Thomas Schwinge" at Oct 08, 2019 12:31:34 PM
Thomas Schwinge wrote:
> In r276692, I committed the attached to "Add back Trevor Smigiel; move
> into Write After Approval section", assuming that it was just an
> oversight that he got dropped from the file, as he -- in contrast to
> David and Ulrich -- doesn't remain listed with other roles.
Ah, you're right -- thanks for catching this!
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2019-10-08 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 20:17 Ulrich Weigand
2019-09-03 14:16 ` Jeff Law
2019-10-28 9:38 ` Eric Botcazou
2019-10-08 10:32 ` Thomas Schwinge
2019-10-08 16:29 ` Ulrich Weigand [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=20191008162902.97505D802F5@oc3748833570.ibm.com \
--to=uweigand@de.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas@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).