From: Ian Lance Taylor <iant@google.com>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: Andrey Belevantsev <abel@ispras.ru>,
Pierre Vittet <piervit@pvittet.com>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, MELT] correcting path error in the Makefile.in
Date: Wed, 18 May 2011 17:01:00 -0000 [thread overview]
Message-ID: <mcrd3jgt5sl.fsf@coign.corp.google.com> (raw)
In-Reply-To: <20110518083742.GA28368@ours.starynkevitch.net> (Basile Starynkevitch's message of "Wed, 18 May 2011 10:37:42 +0200")
Basile Starynkevitch <basile@starynkevitch.net> writes:
> On Wed, May 18, 2011 at 10:27:11AM +0400, Andrey Belevantsev wrote:
>
>> On 17.05.2011 23:42, Basile Starynkevitch wrote:
>> >On Tue, 17 May 2011 21:30:44 +0200
>> >Pierre Vittet<piervit@pvittet.com> wrote:
>>
>> >>My contributor number is 634276.
>> You don't have to write your FSF contributor number in each mail to
>> gcc-patches. This information is irrelevant to anybody reading the
>> list as soon as you have got your papers right and got acquainted
>> with the community. So don't worry about this :)
>
>
> It would help a lot if Pierre Vittet had a write access to the SVN of GCC.
> Hese legal papers are done. However, neither Pierre nor me understands how
> can he get an actual write access to the SVN (that is an SSH account on
> gcc.gnu.org). Apparently, Pierre needs to be presented (or introduced) by someone. But a plain write after approval GCC maintainer like me is not enough.
>
> So how can Pierre get write access to GCC ?
We usually like to see a few successful patches before granting people
write access, to make sure that people have the mechanics down before
they start changing the repository.
Ian
prev parent reply other threads:[~2011-05-18 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 5:55 Pierre Vittet
2011-05-18 6:04 ` Basile Starynkevitch
[not found] ` <4DD366BF.1010109@ispras.ru>
2011-05-18 11:30 ` Basile Starynkevitch
2011-05-18 17:01 ` Ian Lance Taylor [this message]
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=mcrd3jgt5sl.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=abel@ispras.ru \
--cc=basile@starynkevitch.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=piervit@pvittet.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).