public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Georg-Johann Lay <avr@gjlay.de>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: "Weddington, Eric" <Eric.Weddington@atmel.com>,
	 gcc-patches@gcc.gnu.org, Anatoly Sokolov <aesok@post.ru>,
	 Denis Chertykov <chertykov@gmail.com>
Subject: Re: [Ping #2][Patch, testsuite]: Don't xfail sibcalls on AVR
Date: Fri, 08 Apr 2011 09:30:00 -0000	[thread overview]
Message-ID: <4D9ED5B5.4030208@gjlay.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1104070124090.6055@gerinyyl>

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

  reply	other threads:[~2011-04-08  9:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  9:38 [Ping][Patch, " Georg-Johann Lay
2011-04-05  9:06 ` [Ping #2][Patch, " Georg-Johann Lay
2011-04-05 23:01   ` Weddington, Eric
2011-04-06 10:54     ` Georg-Johann Lay
2011-04-06 12:19       ` Weddington, Eric
2011-04-06 12:55         ` Georg-Johann Lay
2011-04-06 23:26           ` Gerald Pfeifer
2011-04-08  9:30             ` Georg-Johann Lay [this message]
2011-04-09  7:30               ` Ralf Wildenhues
2011-04-09 15:40                 ` Gerald Pfeifer
2011-04-08 23:18 ` [Ping][Patch, " Weddington, Eric

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=4D9ED5B5.4030208@gjlay.de \
    --to=avr@gjlay.de \
    --cc=Eric.Weddington@atmel.com \
    --cc=aesok@post.ru \
    --cc=chertykov@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.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).