This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Ping #2][Patch, testsuite]: Don't xfail sibcalls on AVR


Gerald Pfeifer schrieb:
> On Wed, 6 Apr 2011, Georg-Johann Lay wrote:
>> I signed a fsf copyright assignment. AFAIK there is no automatism
>> that grants write access when copyright assignment is approved.
> 
> Yes, this is correct.
> 
>> I would have to be maintainer or something like that.
> 
> Nope.  All you need is a maintainer (Eric, Denis and Anatoly all
> qualifying) to sponsor your request.  Obviously that mostly makes
> sense if you expect to contribute more than a handfull of patches
> over the course of the next year, which we do hope will be the
> case. :-)
> 
> Gerald

Thanks for that hint. Is that the "Write after Approval" section in
MAINTAINERS?

Having write permissions would make thinks easier, both for the
maintainers and for me, I think.

However, I have bunch of questions for that I don't find answers in
the wiki. As it is very easy *not* to find something in the gcc wiki,
I probably just missed it...

1) What is the exact procedure for this? Will it be like fsf copyright
   assignment and take more than a year (at least in my case) to pass?

2) Changelogs and svn logs are always in sync. Is there some setup
   in the svn server to do this magic? Are there custom scripts for
   this or is it all hand-made?

3) Ditto for PRs that get a notification as soon as a patch goes
   upstream.

4) Will there be someone like a mentor who I could ask such
   questions or get useful hints?

Johann


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]