GDB CVS repository read/write access request

GDB CVS repository read/write access request

[Jan Kratochvil]

Dear developers,

as a GDB contributor with several accepted patches (please see GDB ChangeLogs)
I would like direct CVS read/write access to the reposities "gdb" and "src".

Sure I am going to get a review first on <gdb-patches@sourceware.org>.
Various typo fixing patches could be also committed directly.


Thanks,
Jan

Re: GDB CVS repository read/write access request

[Christopher Faylor]

On Fri, Jan 19, 2007 at 03:31:15PM +0100, Jan Kratochvil wrote:
>as a GDB contributor with several accepted patches (please see GDB ChangeLogs)
>I would like direct CVS read/write access to the reposities "gdb" and "src".
>
>Sure I am going to get a review first on <gdb-patches@sourceware.org>.
>Various typo fixing patches could be also committed directly.

Sorry, but it doesn't work like this.  You need to be sponsored by a
current gdb developer.  You can't just nominate yourself.

cgf

Re: GDB CVS repository read/write access request

[Andrew Cagney]

Chris,

I'm not sure what you mean by sponsorship.

 From gdb/MAINTAINERS:
To get recommended for the Write After Approval list you need a valid 
FSF assignment and have submitted one good patch.

So, to the best of my knowledge, the ability to commit to GDB continues 
to be based solely on demonstrated technical merit ;-)  In the case of 
Jan, he as an assignment through Red Hat and has been submitting good 
patches on and off for some 6 months now.

While as a co-worker I'm certainly reluctant to be the one making this 
nomination, I do think delaying this 6 months is sufficient.  If this is 
unreasonable then Jan and I are more than happy to continue waiting 
until someone sees fit to put him forward for GDB's write-after-approval 
list.

Andrew

Christopher Faylor wrote:
> On Fri, Jan 19, 2007 at 03:31:15PM +0100, Jan Kratochvil wrote:
>   
>> as a GDB contributor with several accepted patches (please see GDB ChangeLogs)
>> I would like direct CVS read/write access to the reposities "gdb" and "src".
>>
>> Sure I am going to get a review first on <gdb-patches@sourceware.org>.
>> Various typo fixing patches could be also committed directly.
>>     
>
> Sorry, but it doesn't work like this.  You need to be sponsored by a
> current gdb developer.  You can't just nominate yourself.
>
> cgf
>   

Re: GDB CVS repository read/write access request

[cgf-please-use-the-mailinglist]

On Fri, Jan 19, 2007 at 11:27:40AM -0500, Andrew Cagney wrote:
>Chris,
>
>I'm not sure what you mean by sponsorship.
>
From gdb/MAINTAINERS:
>To get recommended for the Write After Approval list you need a valid 
>FSF assignment and have submitted one good patch.
>
>So, to the best of my knowledge, the ability to commit to GDB continues 
>to be based solely on demonstrated technical merit ;-)  In the case of 
>Jan, he as an assignment through Red Hat and has been submitting good 
>patches on and off for some 6 months now.
>
>While as a co-worker I'm certainly reluctant to be the one making this 
>nomination, I do think delaying this 6 months is sufficient.  If this is 
>unreasonable then Jan and I are more than happy to continue waiting 
>until someone sees fit to put him forward for GDB's write-after-approval 
>list.

Personally, I'm not going to automatically grant someone access to
sourceware repositories just because they seem to think that they
deserve it.

If the OP had included a few clues, like the fact that they already had
an account on sourceware, what the account was, and clearly stated that you
were approving the access, then we could have avoided this back-and-forth.

Anyway, I've added jkratoch to the src and gdb groups.

cgf

Re: GDB CVS repository read/write access request

[Jan Kratochvil]

Dear Christopher,

On Fri, 19 Jan 2007 19:34:06 +0100, cgf-please-use-the-mailinglist@sourceware.org wrote:
[snip]
> If the OP had included a few clues, like the fact that they already had
> an account on sourceware, what the account was, and clearly stated that you
> were approving the access, then we could have avoided this back-and-forth.

apologies, I was not aware of all the steps and I could write the mail better.


> Anyway, I've added jkratoch to the src and gdb groups.

Acknowledging working write permissions.  Added myself to `gdb/MAINTAINERS'.



Thanks,
Jan