This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] PR jit/63969: Fix segfault in error-handling when driver isn't found
- From: Mike Stump <mikestump at comcast dot net>
- To: David Malcolm <dmalcolm at redhat dot com>
- Cc: Gcc Patch List <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 19 Nov 2014 23:09:13 -0800
- Subject: Re: [PATCH] PR jit/63969: Fix segfault in error-handling when driver isn't found
- Authentication-results: sourceware.org; auth=none
- References: <1416464586 dot 11511 dot 6 dot camel at surprise>
On Nov 19, 2014, at 10:23 PM, David Malcolm <dmalcolm@redhat.com> wrote:
> It's not clear to me if I can approve my own patches to the jit
So, to answer that, we look at MAINTAINERS, and look up your name:
Various Maintainers
jit David Malcolm <dmalcolm@redhat.com>
So, this means that you can review other peoples work and approve it for the jit code, and you can review and approve your own work for the jit code. This is the definition of Maintainer. If you had been listed under Reviewers, you would need approval for your own work.
Now, that doesn’t mean, you can’t ask for a review for any reason you want. :-)