From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Mike Stump <mikestump@comcast.net>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 09/14] Add D2 Testsuite Dejagnu files.
Date: Fri, 21 Sep 2018 20:17:00 -0000 [thread overview]
Message-ID: <CABOHX+d06HTuMyhOc=hxAhT0C8g9w7m-8tpRwfqgPZ+=PEi=wg@mail.gmail.com> (raw)
In-Reply-To: <94886957-3E71-4F45-BE0F-9044EBF0A570@comcast.net>
On 21 September 2018 at 22:04, Mike Stump <mikestump@comcast.net> wrote:
> On Sep 19, 2018, at 1:36 PM, Iain Buclaw <ibuclaw@gdcproject.org> wrote:
>>
>> On 18 September 2018 at 02:36, Iain Buclaw <ibuclaw@gdcproject.org> wrote:
>>>
>>> This patch adds D language support to the GCC testsuite.
>>>
>>> As well as generating the DejaGNU options for compile and link tests,
>>> handles the conversion from DMD-style compiler options to GDC.
>>
>> https://gcc.gnu.org/ml/gcc-patches/2017-08/msg00112.html
>>
>> I take it from the comment in the last review, that I can self-approve
>> this, and the other testsuite related patches.
>
> If you're a maintainer for D... :-) Presently, you're not listed as maintainer. If appointed, then you will modify MAINTAINERS and move your entry up and put D front end on the line. In the time span between the two events I'd punt to the SC. If you have been appointed, yes, that remains until you step down or the SC changes their mind or some other big event. You can also ask for advice or ask for a review, even if you can approve.
I have been appointed maintainer when the D language was accepted for
inclusion. I have been delaying adding myself to MAINTAINERS until all
this work is signed off.
Iain
next prev parent reply other threads:[~2018-09-21 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 0:37 Iain Buclaw
2018-09-19 20:40 ` Iain Buclaw
2018-09-21 20:14 ` Mike Stump
2018-09-21 20:17 ` Iain Buclaw [this message]
2018-09-21 20:04 ` Mike Stump
2018-10-22 6:12 ` Iain Buclaw
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='CABOHX+d06HTuMyhOc=hxAhT0C8g9w7m-8tpRwfqgPZ+=PEi=wg@mail.gmail.com' \
--to=ibuclaw@gdcproject.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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).