public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, Jakub Jelinek <jakub@redhat.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
	       "Zamyatin, Igor" <igor.zamyatin@intel.com>,
	       "Iyer, Balaji V" <balaji.v.iyer@intel.com>,
	       "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Listing a maintainer for libcilkrts, and GCC's Cilk Plus implementation generally?
Date: Thu, 05 Mar 2015 20:39:00 -0000	[thread overview]
Message-ID: <54F8BF10.2070701@redhat.com> (raw)
In-Reply-To: <CAMe9rOpaNrtjv2N=dKALK7Cod8BOhQxJ4xbxdtxQDbuk14iOyA@mail.gmail.com>

On 02/23/15 14:41, H.J. Lu wrote:
> On Mon, Sep 29, 2014 at 4:00 AM, Jakub Jelinek <jakub@redhat.com> wrote:
>> On Mon, Sep 29, 2014 at 12:56:06PM +0200, Thomas Schwinge wrote:
>>> Hi!
>>>
>>> On Tue, 23 Sep 2014 11:02:30 +0000, "Zamyatin, Igor" <igor.zamyatin@intel.com> wrote:
>>>> Jeff Law wrote:
>>>>> The original plan was for Balaji to take on this role; however, his assignment
>>>>> within Intel has changed and thus he's not going to have time to work on
>>>>> Cilk+ anymore.
>>>>>
>>>>> Igor Zamyatin has been doing a fair amount of Cilk+ maintenance/bugfixing
>>>>> and it might make sense for him to own it in the long term if he's interested.
>>>>
>>>> That's right.
>>>
>>> Thanks!
>>>
>>>> Can I add 2 records (cilk plus and libcilkrts) to Various Maintainers section?
>>>
>>> I understand Jeff's email as a pre-approval of such a patch.
>>
>> I think only SC can appoint maintainers, and while Jeff is in the SC,
>> my reading of that mail wasn't that it was the SC that has acked that, but
>> rather a question if Igor is willing to take that role, which then would
>> need to be acked by SC.
>>
>
> Where are we on this?  Do we have a maintainer for Cilk Plus
> and its run-time library?
Not at this time.  There was a bit of blockage on various things with 
the steering committee (who approves maintainers).  I've got a 
half-dozen or so proposals queued (including Cilk maintainership).

Jeff

  reply	other threads:[~2015-03-05 20:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 14:06 Thomas Schwinge
2014-09-22 14:35 ` Make name+email address cut'n'paste-able (was: Listing a maintainer for libcilkrts, and GCC's Cilk Plus implementation generally?) Jan-Benedict Glaw
2014-09-22 16:42   ` Make name+email address cut'n'paste-able Jeff Law
2014-09-22 17:08 ` Listing a maintainer for libcilkrts, and GCC's Cilk Plus implementation generally? Jeff Law
2014-09-23 11:18   ` Zamyatin, Igor
2014-09-29 11:00     ` Thomas Schwinge
2014-09-29 11:09       ` Jakub Jelinek
2014-09-29 13:10         ` Thomas Schwinge
2015-02-23 21:41         ` H.J. Lu
2015-03-05 20:39           ` Jeff Law [this message]
2015-03-06  0:42             ` Thomas Schwinge
2015-03-06 14:26               ` Tannenbaum, Barry M
2015-03-06 14:37                 ` Zamyatin, Igor
2015-03-06 17:13               ` Jeff Law
2016-03-29 15:10                 ` Thomas Schwinge

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=54F8BF10.2070701@redhat.com \
    --to=law@redhat.com \
    --cc=balaji.v.iyer@intel.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=igor.zamyatin@intel.com \
    --cc=jakub@redhat.com \
    --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).