From: Christopher Faylor <cgf@redhat.com>
To: Jonathan Larmour <jifl@jifvik.org>
Cc: overseers@sources.redhat.com, geoffk@apple.com
Subject: Re: problem with form for applying for cvs write privileges
Date: Thu, 30 Jan 2003 18:34:00 -0000 [thread overview]
Message-ID: <20030130183500.GA7039@redhat.com> (raw)
In-Reply-To: <3E394421.6040103@jifvik.org>
On Thu, Jan 30, 2003 at 03:26:25PM +0000, Jonathan Larmour wrote:
>Christopher Faylor wrote:
>>In the case of Red Hat folks the policy *is* followed strictly. When
>>sourceware was first set up ages ago, I believe every engineer in
>>Cygnus had an account on it.
>
><nitpick>Toolchain engineers maybe, but not all engineers.</nitpick>
Oh. Didn't know that. That's strange given some of the folks I saw in
/etc/passwd.
cgf
next prev parent reply other threads:[~2003-01-30 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 22:13 Caroline Tice
2003-01-30 9:35 ` Gerald Pfeifer
2003-01-30 15:08 ` Christopher Faylor
2003-01-30 15:26 ` Jonathan Larmour
2003-01-30 15:31 ` law
2003-01-30 18:35 ` Christopher Faylor
2003-01-30 18:34 ` Christopher Faylor [this message]
2003-01-30 15:26 ` Gerald Pfeifer
2003-01-30 16:01 ` Andrew Cagney
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=20030130183500.GA7039@redhat.com \
--to=cgf@redhat.com \
--cc=geoffk@apple.com \
--cc=jifl@jifvik.org \
--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).