Add to maintainers list.

Add to maintainers list.

[Alex Velenko]

[-- Attachment #1: Type: text/plain, Size: 585 bytes --]


2014-11-20  Alex Velenko  <Alex.Velenko@arm.com>

	*MAINTAINERS (write-after-approval): Add myself.

diff --git a/MAINTAINERS b/MAINTAINERS
index 11a28ef..eada4e9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -566,6 +566,7 @@ David Ung					<davidu@mips.com>
 Neil Vachharajani				<nvachhar@gmail.com>
 Kris Van Hees					<kris.van.hees@oracle.com>
 Joost VandeVondele				<joost.vandevondele@mat.ethz.ch>
+Alex Velenko					<alex.velenko@arm.com>
 Ilya Verbin					<iverbin@gmail.com>
 Kugan Vivekanandarajah				<kuganv@linaro.org>
 Tom de Vries					<tom@codesourcery.com>

Re: Add to maintainers list.

[Alex Velenko]

Hi,

>
> 2014-11-20  Alex Velenko  <Alex.Velenko@arm.com>
>
> 	*MAINTAINERS (write-after-approval): Add myself.
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 11a28ef..eada4e9 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -566,6 +566,7 @@ David Ung					<davidu@mips.com>
>   Neil Vachharajani				<nvachhar@gmail.com>
>   Kris Van Hees					<kris.van.hees@oracle.com>
>   Joost VandeVondele				<joost.vandevondele@mat.ethz.ch>
> +Alex Velenko					<alex.velenko@arm.com>
>   Ilya Verbin					<iverbin@gmail.com>
>   Kugan Vivekanandarajah				<kuganv@linaro.org>
>   Tom de Vries					<tom@codesourcery.com>
>

Can someone, please, approve?
Kind regards,
Alex

Re: Add to maintainers list.

[Marcus Shawcroft]

On 20 November 2014 16:27, Alex Velenko <alex.velenko@arm.com> wrote:
>
> 2014-11-20  Alex Velenko  <Alex.Velenko@arm.com>
>
>         *MAINTAINERS (write-after-approval): Add myself.
>

Your patch looks fine, commit it.  /Marcus

Re: Add to maintainers list.

[Gerald Pfeifer]

Hi Alex,

On Friday 2014-11-21 10:07, Alex Velenko wrote:
> Can someone, please, approve?

we tried to document this in https://gcc.gnu.org/svnwrite.html .

Can you perhaps suggest a way for us to improve this to make
it more clear or easier to find?

Gerald

Re: Add to maintainers list.

[Tom de Vries]

On 24-01-15 20:41, Gerald Pfeifer wrote:
> Hi Alex,
>
> On Friday 2014-11-21 10:07, Alex Velenko wrote:
>> Can someone, please, approve?
>
> we tried to document this in https://gcc.gnu.org/svnwrite.html .
>
> Can you perhaps suggest a way for us to improve this to make
> it more clear or easier to find?
>

How about this?

Thanks,
- Tom

diff --git a/MAINTAINERS b/MAINTAINERS
index 05cf4cd..c39dbae 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -597,6 +597,10 @@ Jon Ziegler 
<jonz@apple.com>
  Roman Zippel                                   <zippel@linux-m68k.org>
  Josef Zlomek                                   <josef.zlomek@email.cz>

+Note that after receiving write approval, no patch approval is needed to add
+yourself to the Write-After-Approval list.  See also
+https://gcc.gnu.org/svnwrite.html#authenticated.
+
  Bug database only accounts

  James Dennett                                  <jdennett@acm.org>

Re: Add to maintainers list.

[Mike Stump]

On Jan 25, 2015, at 2:10 AM, Tom de Vries <Tom_deVries@mentor.com> wrote:
> On 24-01-15 20:41, Gerald Pfeifer wrote:
>> Hi Alex,
>> 
>> On Friday 2014-11-21 10:07, Alex Velenko wrote:
>>> Can someone, please, approve?
>> 
>> we tried to document this in https://gcc.gnu.org/svnwrite.html .
>> 
>> Can you perhaps suggest a way for us to improve this to make
>> it more clear or easier to find?
>> 
> 
> How about this?

I’d rather not.  Policy should go into the policy page, and if people can’t read and understand the policy page and ask about policy anyway, then that is a good thing.  We can point them back at the policy page and they can read it again.  Edits to policy should go into the policy page.  That way, one can read just the policy page and keep up.  Anyway, that’s my take.