From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3171 invoked by alias); 22 Jan 2003 20:53:29 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 3152 invoked from network); 22 Jan 2003 20:53:29 -0000 Received: from unknown (HELO monty-python.gnu.org) (199.232.76.173) by 172.16.49.205 with SMTP; 22 Jan 2003 20:53:29 -0000 Received: from vexpert.dbai.tuwien.ac.at ([128.130.111.12]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18bRqD-0005iy-00 for overseers@gcc.gnu.org; Wed, 22 Jan 2003 15:51:21 -0500 Received: from [128.130.111.39] (acrux [128.130.111.39]) by vexpert.dbai.tuwien.ac.at (8.12.6/8.12.6) with ESMTP id h0MKgGB5025805 for ; Wed, 22 Jan 2003 21:42:16 +0100 (CET) Date: Wed, 22 Jan 2003 20:53:00 -0000 From: Gerald Pfeifer To: overseers@gcc.gnu.org Subject: Re: Welcome to gcc.gnu.org In-Reply-To: <20030122174634.21612.qmail@sources.redhat.com> Message-ID: References: <20030122174634.21612.qmail@sources.redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003-q1/txt/msg00182.txt.bz2 (Some notes regarding our welcome message for new accounts.) On Wed, 22 Jan 2003 root@sources.redhat.com wrote: > Your account is now active, the login name is reichelt@gcc.gnu.org. > [...] > 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. Perhaps we ought to remove the part about laughin evilly? Not all (new) contributors might grok this kind of humor... > You should now have write access to the gcc repository with > SSH+cvs. Here are lots of details about how to do things. s/gcc/GCC/ s/cvs/CVS/ > Regarding SSH: By default, gcc.gnu.org uses ssh protcol 1. If you ^^^^^^^^^ > have keys in your .ssh directory which will also work with protocol 2, > you will need to add the following lines to your a .ssh/config > directory: > > Host gcc.gnu.org > Protocol 1 There's a typo here, but in general: Do we still have the Protocol 1 requirement? (I have been using Protocol 2 for several months with gcc.gnu.org, not the least because it's more secure.) Gerald