From: law@redhat.com
To: cgd@netbsd.org (Chris G. Demetriou)
Cc: overseers@sources.redhat.com
Subject: Re: Request from Chris Demetriou
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <13343.974852107@upchuck> (raw)
In-Reply-To: <87em05jfjs.fsf@mail.netbsd.org>
In message < 87em05jfjs.fsf@mail.netbsd.org >you write:
> Two questions:
>
> (1) seems that this is a cvs-only account. No problem with that, but
> could i have you add the following additional authorized key:
>
> 1024 33 1099239929804193115914405165337274956993964691247972631606443719141
> 633720841357862435930194452430331665099777648408292322355332219967733921647
> 689100253152019582073438392593074682752341724505984452485340681872170841819
> 482390026887040578752162508444706646163362979825045975205661829856849757527
> 28062613462603429 cgd@kickme.demetriou.com
Done.
> (2) Does the account (and write-after-approval access for binutils)
> also give me write-after-approval access for e.g. gcc as well. (I
> figure it probably does technically, but possibly not
> 'politically.' 8-)
Normally the answer would be no. However, I botched things and put you in
the wrong default group. Rather than fix it, I just left it since we'll
probably want you to have gcc access soon too :-)
jeff
WARNING: multiple messages have this Message-ID
From: law@redhat.com
To: cgd@netbsd.org (Chris G. Demetriou)
Cc: overseers@sources.redhat.com
Subject: Re: Request from Chris Demetriou
Date: Tue, 21 Nov 2000 16:13:00 -0000 [thread overview]
Message-ID: <13343.974852107@upchuck> (raw)
Message-ID: <20001121161300.lJ5qxAn_iS6QnoAmPpEBcvNqyixA1_j-NsVBXdbeN1E@z> (raw)
In-Reply-To: <87em05jfjs.fsf@mail.netbsd.org>
In message < 87em05jfjs.fsf@mail.netbsd.org >you write:
> Two questions:
>
> (1) seems that this is a cvs-only account. No problem with that, but
> could i have you add the following additional authorized key:
>
> 1024 33 1099239929804193115914405165337274956993964691247972631606443719141
> 633720841357862435930194452430331665099777648408292322355332219967733921647
> 689100253152019582073438392593074682752341724505984452485340681872170841819
> 482390026887040578752162508444706646163362979825045975205661829856849757527
> 28062613462603429 cgd@kickme.demetriou.com
Done.
> (2) Does the account (and write-after-approval access for binutils)
> also give me write-after-approval access for e.g. gcc as well. (I
> figure it probably does technically, but possibly not
> 'politically.' 8-)
Normally the answer would be no. However, I botched things and put you in
the wrong default group. Rather than fix it, I just left it since we'll
probably want you to have gcc access soon too :-)
jeff
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 cgd
2000-11-20 21:35 ` cgd
2000-12-30 6:08 ` law
2000-11-21 10:39 ` law
2000-12-30 6:08 ` Chris G. Demetriou
2000-11-21 11:24 ` Chris G. Demetriou
2000-12-30 6:08 ` law [this message]
2000-11-21 16:13 ` law
2008-03-22 18:05 cgd
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=13343.974852107@upchuck \
--to=law@redhat.com \
--cc=cgd@netbsd.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).