This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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: how to get read/write access for profile extension contributor

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Ian Lance Taylor <iant at google dot com>
Cc: Silvius Rus <rus at google dot com>, libstdc++ at gcc dot gnu dot org, Changhee Jung <haemil99 at gmail dot com>
Date: Fri, 27 Nov 2009 16:49:58 -0800
Subject: Re: how to get read/write access for profile extension contributor
References: <e90dbffc0911252155t1e79d7d2p24e597fdda0f848d@mail.gmail.com> <mcrfx8059qj.fsf@dhcp-172-17-9-151.mtv.corp.google.com>

 
> But the general guideline for write access to the SVN tree is
> successful submission of a couple of patches.  That ensures that the
> contributor understands gcc's submission and commit policy to at least
> a minimal degree.  Write access is a powerful tool, since we must
> essentially trust everybody with write access, so the gcc maintainers
> don't normally give it out on spec.

Yep. 

Let's try to work the kinks out with the first couple of patches,
and then when everything looks good after a bit re-discuss.

-benjamin

Follow-Ups:
- Re: how to get read/write access for profile extension contributor
  - From: Silvius Rus

References:
- how to get read/write access for profile extension contributor
  - From: Silvius Rus
- Re: how to get read/write access for profile extension contributor
  - From: Ian Lance Taylor

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