From: Hans-Peter Nilsson <hp@bitrange.com>
To: Christopher Faylor <cgf@redhat.com>
Cc: overseers@sources.redhat.com
Subject: Re: Problem sending request for RW access to GCC CVS
Date: Tue, 16 Sep 2003 19:39:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.44.0309161519180.94482-200000@dair.pair.com> (raw)
In-Reply-To: <20030916171058.GF18774@redhat.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 489 bytes --]
On Tue, 16 Sep 2003, Christopher Faylor wrote:
> On Tue, Sep 16, 2003 at 12:56:40PM -0400, Christopher Faylor wrote:
> Is this YA case of someone not realizing that gcc.gnu.org and
> sources.redhat.com are one and the same? You could have saved both
> of us some work by just saying that you had an existing account and
> needed access to gcc.
Here's a patch to save even more work. The email address is a
tweaking item and I couldn't bring myself to make it a mailto
link.
brgds, H-P
[-- Attachment #2: ps_form.cgi-patch --]
[-- Type: TEXT/PLAIN, Size: 645 bytes --]
--- ps_form.cgi.old Tue Sep 16 21:24:26 2003
+++ ps_form.cgi Tue Sep 16 21:36:28 2003
@@ -77,6 +77,10 @@ To have cvs access to a project hosted o
<li>Who approved your access
<li>An SSH public key, generated with ssh-keygen
</ol>
+If you <em>already have</em> an account on sources.redhat.com or
+gcc.gnu.org for CVS write access, then do not use this form. Instead send
+an email to overseers (at) sourceware.org telling what project you want
+write access to and who approved that access.<br><br>
If you don't have SSH set up and installed already, we
recommend using <a href="http://www.openssh.com">OpenSSH</a>.
<br><br>
next prev parent reply other threads:[~2003-09-16 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 16:40 Joel Brobecker
2003-09-16 16:56 ` Christopher Faylor
2003-09-16 17:11 ` Christopher Faylor
2003-09-16 17:50 ` Joel Brobecker
2003-09-16 19:39 ` Hans-Peter Nilsson [this message]
2003-09-16 20:21 ` 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=Pine.BSF.4.44.0309161519180.94482-200000@dair.pair.com \
--to=hp@bitrange.com \
--cc=cgf@redhat.com \
--cc=overseers@sources.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).