From: Jeff Law <law@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>,
"Iyer, Balaji V" <balaji.v.iyer@intel.com>,
gcc@gcc.gnu.org
Subject: Re: Listing a maintainer for libcilkrts, and GCC's Cilk Plus implementation generally?
Date: Mon, 22 Sep 2014 17:08:00 -0000 [thread overview]
Message-ID: <54205555.5040506@redhat.com> (raw)
In-Reply-To: <87r3z33g2q.fsf@kepler.schwinge.homeip.net>
On 09/22/14 08:06, Thomas Schwinge wrote:
> Hi!
>
> As has been noted before,
> <http://news.gmane.org/find-root.php?message_id=%3Cyddhabgief1.fsf%40lokon.CeBiTec.Uni-Bielefeld.DE%3E>,
> 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
next prev parent reply other threads:[~2014-09-22 16:59 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 ` Jeff Law [this message]
2014-09-23 11:18 ` Listing a maintainer for libcilkrts, and GCC's Cilk Plus implementation generally? 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
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=54205555.5040506@redhat.com \
--to=law@redhat.com \
--cc=balaji.v.iyer@intel.com \
--cc=gcc@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).