From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2401 invoked by alias); 22 Sep 2014 16:59:07 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 2392 invoked by uid 89); 22 Sep 2014 16:59:07 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 22 Sep 2014 16:59:06 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s8MGx1M7024675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 22 Sep 2014 12:59:02 -0400 Received: from stumpy.slc.redhat.com (ovpn-113-38.phx2.redhat.com [10.3.113.38]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s8MGx1aF032588; Mon, 22 Sep 2014 12:59:01 -0400 Message-ID: <54205555.5040506@redhat.com> Date: Mon, 22 Sep 2014 17:08:00 -0000 From: Jeff Law User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: Thomas Schwinge , "Iyer, Balaji V" , gcc@gcc.gnu.org Subject: Re: Listing a maintainer for libcilkrts, and GCC's Cilk Plus implementation generally? References: <87r3z33g2q.fsf@kepler.schwinge.homeip.net> In-Reply-To: <87r3z33g2q.fsf@kepler.schwinge.homeip.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-09/txt/msg00316.txt.bz2 On 09/22/14 08:06, Thomas Schwinge wrote: > Hi! > > As has been noted before, > , > GCC's MAINTAINERS file does not list a maintainer for libcilkrts, or > GCC's Cilk Plus implementation generally. Shouldn't it? I regularely > consult this file when reporting issues in specific parts of the GCC code > base. 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. jeff