From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Ian Lance Taylor <ian@airs.com>
Cc: overseers@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>,
Tom Tromey <tromey@redhat.com>
Subject: Re: write access to the GCC repository
Date: Wed, 13 Feb 2008 15:11:00 -0000 [thread overview]
Message-ID: <20080213142358.GC28594@ins.uni-bonn.de> (raw)
In-Reply-To: <m38x1pndzu.fsf@gossamer.airs.com>
Hello Ian,
* Ian Lance Taylor wrote on Wed, Feb 13, 2008 at 03:10:45PM CET:
> Ralf Wildenhues wrote on Fri, Feb 08, 2008 at 05:58:36PM CET:
>
> > sponsored by Gerald Pfeifer (Cc:ed), I would like to ask for write
> > access to the GCC repository. [...]
> I have added you to the gcc group.
Thank you. I will try it out tonight.
> > While we're at it, my write access to the Automake GNAT on
> > sourceware.org seems to have died again, meaning that I cannot log
> > in in edit mode to make changes (marking PRs as fixed, etc).
>
> I'm not sure how to fix this--anybody know?
Cc:ing Tom Tromey, he fixed that last time. FWIW, this is what happened
back then (and yes, a new password would be good, too):
| * Tom Tromey wrote:
| >>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
|
| Daniel> Hrm, the rwild entry is below the * entry in the gnatsd.access. Is
| Daniel> that valid?
|
| I moved Ralf's entry up above this one, on the theory that maybe this
| theory is correct.
Cheers, and thanks,
Ralf
next prev parent reply other threads:[~2008-02-13 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 17:13 Ralf Wildenhues
2008-02-13 14:11 ` Ralf Wildenhues
2008-02-13 14:24 ` Ian Lance Taylor
2008-02-13 15:11 ` Ralf Wildenhues [this message]
2008-02-13 17:40 ` Tom Tromey
2008-02-14 20:22 ` Ralf Wildenhues
2019-01-17 16:27 Write " Kwok Cheung Yeung
2019-01-17 19:03 ` Christopher Faylor
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=20080213142358.GC28594@ins.uni-bonn.de \
--to=ralf.wildenhues@gmx.de \
--cc=gerald@pfeifer.com \
--cc=ian@airs.com \
--cc=overseers@gcc.gnu.org \
--cc=tromey@redhat.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).