public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Quentin Neill <quentin.neill.gnu@gmail.com>
To: overseers@gcc.gnu.org
Cc: qneill@sourceware.org, spop@gcc.gnu.org
Subject: Re: Welcome to sourceware.org
Date: Wed, 17 Nov 2010 00:18:00 -0000	[thread overview]
Message-ID: <AANLkTikpX-h2YwfCzgNa3L_16x1B-DZYSsCPd_Yj=7Qd@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikyurHkbdcRAOuHEKJTS1aY-d85J-4jnc529Qkp@mail.gmail.com>

On Tue, Nov 9, 2010 at 1:58 PM, Quentin Neill
<quentin.neill.gnu@gmail.com> wrote:
> On Tue, Aug 3, 2010 at 3:30 PM,  <zroot@sourceware.org> wrote:
>> Your account is now active, the login name is qneill@sourceware.org.
>> Mail sent to that address is forwarded to quentin.neill.gnu@gmail.com.
> Hi,
>
> I am sending this email to request for access to the GCC repository
> according to http://gcc.gnu.org/svnwrite.html#authenticated
>
> I have a sourceware account, the ID is qneill as shown above.
>
> Sebastian Pop will be sponsoring my access.
> --
> Quentin Neill
> quentin.neill.gnu@gmail.com

Ping?

Kindly revisit this request for GCC repository write access.  I just
tried committing a change to the MAINTAINERS file and got:
    svn: Can't open file '/svn/gcc/db/txn-current-lock': Permission denied

Perhaps I'm in the wrong unix group?
-- 
Quentin




I've been trying to sort out the history (between bugzilla account
creation and confusion with sourceware.org vs. gcc.gnu.org), but I've
concluded that I still don't have GCC svn repository access.

BTW, should I get an email like this but for qneill@gcc.gnu.org and SVN?

On Tue, Aug 3, 2010 at 1:30 PM,  <zroot@sourceware.org> wrote:
> Your account is now active, the login name is qneill@sourceware.org.
> Mail sent to that address is forwarded to quentin.neill.gnu@gmail.com.
> This forwarding is a convenience so that people who reply directly to CVS
> commit mail notes will not get a bounce--publicize it at your own risk.
> If your involvement with the project ends at some point, the mail address
> will become invalid and I will laugh evilly as people try in vain to
> reach you.
>
> You should now have write access to the src repository with
> SSH+CVS.  Here are lots of details about how to do things.

Kindly revisit this request


"Your account is now active, the login name is qneill@sourceware.org.
Mail sent to that address is forwarded to quentin.neill.gnu@gmail.com.
This forwarding is a convenience so that people who reply directly to CVS
commit mail notes will not get a bounce--publicize it at your own risk.
If your involvement with the project ends at some point, the mail address
will become invalid and I will laugh evilly as people try in vain to
reach you."


I'm able to

I sent this email, and thought I received a reply.

But now

  parent reply	other threads:[~2010-11-17  0:18 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
2010-11-18  4:58         ` Ian Lance Taylor
2010-11-18 21:01           ` Quentin Neill
2010-11-17  0:18   ` Quentin Neill [this message]
     [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='AANLkTikpX-h2YwfCzgNa3L_16x1B-DZYSsCPd_Yj=7Qd@mail.gmail.com' \
    --to=quentin.neill.gnu@gmail.com \
    --cc=overseers@gcc.gnu.org \
    --cc=qneill@sourceware.org \
    --cc=spop@gcc.gnu.org \
    /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).