From: Andrew Jenner <andrew@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>, Jeff Law <law@redhat.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
<gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Delete powerpcspe
Date: Mon, 10 Dec 2018 18:25:00 -0000 [thread overview]
Message-ID: <0adf63ed-1fca-cfa1-414b-9b022478b6fd@codesourcery.com> (raw)
In-Reply-To: <20181203214804.GE12380@tucnak>
Sorry for the slow response on this, I was on vacation last week.
On 03/12/2018 21:48, Jakub Jelinek wrote:
> I'd give the maintainers the last week to act if they don't want this
> to happen and if nothing happens, commit it. PR81084 lists all the reasons
> why it should be removed when it is totally unmaintained.
> Just make sure to put stuff that belongs there to gcc/ChangeLog and without
> gcc/ prefixes.
Yes, please go ahead and commit - it's not fair on other maintainers to
have to work around my lack of action on this port. I will continue to
work on it out-of-tree and hope to restore it once it is in proper shape.
Thanks,
Andrew
next prev parent reply other threads:[~2018-12-10 18:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 20:50 Segher Boessenkool
2018-12-03 21:40 ` Jeff Law
2018-12-03 21:49 ` Jakub Jelinek
2018-12-10 18:25 ` Andrew Jenner [this message]
2018-12-10 20:13 ` Segher Boessenkool
2018-12-11 8:44 ` Richard Biener
2018-12-11 13:37 ` Jeff Law
2018-12-12 10:36 ` Richard Biener
2018-12-12 17:33 ` Segher Boessenkool
2018-12-13 16:49 ` Jeff Law
2018-12-14 8:21 ` Segher Boessenkool
2018-12-14 8:43 ` Iain Sandoe
2018-12-14 16:08 ` Jeff Law
2018-12-14 9:52 ` Richard Biener
2018-12-14 16:02 ` Jeff Law
2018-12-14 18:41 ` Joseph Myers
2018-12-14 21:15 ` 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=0adf63ed-1fca-cfa1-414b-9b022478b6fd@codesourcery.com \
--to=andrew@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=law@redhat.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).