From: Christopher Faylor <cgf@redhat.com>
To: Jason Molenda <jason-gcclist@molenda.com>
Cc: Gerald Pfeifer <gerald@pfeifer.com>, overseers@gcc.gnu.org
Subject: Re: Welcome to gcc.gnu.org
Date: Wed, 22 Jan 2003 23:40:00 -0000 [thread overview]
Message-ID: <20030122234137.GA4085@redhat.com> (raw)
In-Reply-To: <20030122152806.A74779@molenda.com>
On Wed, Jan 22, 2003 at 03:28:06PM -0800, Jason Molenda wrote:
>On Wed, Jan 22, 2003 at 09:42:22PM +0100, Gerald Pfeifer wrote:
>
>> > 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...
>
>
>I know it's very English-centric, but I think it's imperative we
>keep this. There's so little humor on the site as it is. Anyone
>who can push a patch past the oft-obstinate gcc and gdb patch
>approval processes MUST have a sense of humor to make it this far. :-)
I agree. I hate to drop the humor on the off chance that someone might
be confused. I haven't heard a single complaint about it, fwiw.
>> > 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.)
>
>
>IIRC it's just a matter of someone upgrading the web form scripts to
>accept the id_dsa.pub style keys. We switched from the last gratis
>protocol-1-only ssh to OpenSSH long ago. Chris has posted on this
>topic in the past, but I think that's the gist of it.
This was one of the things I planned on changing after the new system
was set up. I won't cry if someone beats me to it, though.
cgf
next prev parent reply other threads:[~2003-01-22 23:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030122174634.21612.qmail@sources.redhat.com>
2003-01-22 20:53 ` Gerald Pfeifer
2003-01-22 23:28 ` Jason Molenda
2003-01-22 23:40 ` Christopher Faylor [this message]
2003-01-23 0:09 ` Benjamin Kosnik
[not found] <20141217152934.16213.qmail@sourceware.org>
2014-12-18 22:21 ` Sebastian Huber
2014-12-19 16:14 ` Joel Sherrill
[not found] <20130924144729.26557.qmail@sourceware.org>
2013-11-22 12:04 ` Paulo Matos
[not found] <20030605212847.10833.qmail@sources.redhat.com>
2005-09-08 8:59 ` Daniel Towner
2005-09-08 19:53 ` Ian Lance Taylor
[not found] <20030915134556.13277.qmail@sources.redhat.com>
2003-10-01 9:43 ` Dorit Naishlos
2003-10-01 9:54 ` Gerald Pfeifer
2003-10-01 11:38 ` Dorit Naishlos
2003-10-01 11:22 ` Joseph S. Myers
2003-10-01 12:02 ` Christopher Faylor
2003-10-02 21:43 ` Gerald Pfeifer
2003-10-03 4:01 ` Christopher Faylor
[not found] <20030222192240.25884.qmail@sources.redhat.com>
2003-02-22 19:42 ` Steven Bosscher
[not found] <20010228034610.11379.qmail@sourceware.cygnus.com>
2001-03-10 22:22 ` Craig Rodrigues
2001-03-10 23:43 ` Gerald Pfeifer
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=20030122234137.GA4085@redhat.com \
--to=cgf@redhat.com \
--cc=gerald@pfeifer.com \
--cc=jason-gcclist@molenda.com \
--cc=overseers@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).