From: Sebastian Pop <sebpop@gmail.com>
To: Ian Lance Taylor <ian@airs.com>
Cc: Quentin Neill <quentin.neill.gnu@gmail.com>,
overseers@gcc.gnu.org, qneill@sourceware.org
Subject: Re: Welcome to sourceware.org
Date: Wed, 17 Nov 2010 15:05:00 -0000 [thread overview]
Message-ID: <AANLkTinwbsxQKmQYQuWZCfuSVJFr4qsNN2C8sXpFewyv@mail.gmail.com> (raw)
In-Reply-To: <m3ipzwh23i.fsf@pepe.airs.com>
On Wed, Nov 17, 2010 at 00:54, Ian Lance Taylor <ian@airs.com> wrote:
> Quentin Neill <quentin.neill.gnu@gmail.com> writes:
>
>> I have a patch reviewed and okay'd and ready to commit. Following
>> instructions on GitMirror:
>> http://gcc.gnu.org/wiki/GitMirror#Commit_upstream_.28git-svn.29
>> I get the following:
>>
>> qneill@gold2-simba:~/wk/gcc$ git svn dcommit
>> Committing to svn+ssh://gcc.gnu.org/svn/gcc/trunk ...
>> M gcc/ChangeLog
>> M gcc/config/i386/bmiintrin.h
>> Permission denied: Can't open file '/svn/gcc/db/txn-current-lock':
>> Permission denied at /usr/lib/git-core/git-svn line 570
>>
>> Am I missing something? Do I need to add myself to the MAINTAINERS file?
>
>
> You have write access to the binutils repository, but you do not have
> write access to the gcc repository. They are on the same machine but
> they are managed differently by different people. In order to get write
> access to the gcc repository, you need to follow the guidelines at
> http://gcc.gnu.org/svnwrite.html. Specifically, you need to start with
>
> If you already have an account on sourceware.org, please send email
> to overseers(at)gcc.gnu.org with a request for access to the GCC
> repository. Include the name of an existing maintainer who is
> sponsoring your access and CC: your sponsor.
Quentin has already sent such an email 7 days ago,
but I have not seen a response from overseers yet.
>
> Sebastian, are you sponsoring Quentin for gcc write access?
Yes, I am sponsoring Quentin for GCC write access.
Sebastian
next prev parent reply other threads:[~2010-11-17 15:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100803203035.19633.qmail@sourceware.org>
2010-08-05 23:10 ` Quentin Neill
2010-08-06 8:30 ` Hans-Peter Nilsson
2010-08-06 13:28 ` Christopher Faylor
2010-08-06 16:46 ` Quentin Neill
2010-08-06 17:22 ` Christopher Faylor
2010-08-06 18:22 ` Quentin Neill
2010-11-09 21:59 ` Quentin Neill
2010-11-16 21:02 ` Quentin Neill
2010-11-17 6:54 ` Ian Lance Taylor
2010-11-17 15:05 ` Sebastian Pop [this message]
2010-11-18 4:58 ` Ian Lance Taylor
2010-11-18 21:01 ` Quentin Neill
2010-11-17 0:18 ` Quentin Neill
[not found] <20200402160227.0991B388A01F@sourceware.org>
2020-04-03 6:40 ` Cui, Lili
2020-04-03 11:16 ` Frank Ch. Eigler
[not found] <20110723180027.5293.qmail@sourceware.org>
2011-07-28 0:19 ` Philippe Waroquiers
2011-07-28 0:23 ` Frank Ch. Eigler
[not found] <20080322164357.32125.qmail@sourceware.org>
2008-03-22 19:17 ` Chris Demetriou
2008-03-22 20:05 ` Daniel Jacobowitz
2008-03-22 21:57 ` Christopher Faylor
2008-03-24 16:38 ` Chris Demetriou
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=AANLkTinwbsxQKmQYQuWZCfuSVJFr4qsNN2C8sXpFewyv@mail.gmail.com \
--to=sebpop@gmail.com \
--cc=ian@airs.com \
--cc=overseers@gcc.gnu.org \
--cc=qneill@sourceware.org \
--cc=quentin.neill.gnu@gmail.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).