public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Caroline Tice <ctice@apple.com>
To: overseers@sources.redhat.com
Subject: problem with form for applying for cvs write privileges
Date: Wed, 29 Jan 2003 22:13:00 -0000	[thread overview]
Message-ID: <E3D4612D-33D6-11D7-B45C-000393BB90B6@apple.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]


Hello,

I am a new compiler developer at Apple, and I will be working on the 
Apple version of
gcc (I have already submitted one patch for approval) and will need cvs 
write access for
checking in my changes.

I went  to the form (http;//sources.redhat.com/cgi-bin/pdw/ps_form.cgi 
and tried to enter
the information.  It won't accept my .ssh key.  I believe the problem 
is that my .ssh
key is a protocol 2 key, not a protocol 1 key, and it contains slashes 
which the form is
interpreting as line-breaks rather than characters.

I spoke with Geoffrey Keating (geoffk@apple.com) about the problem and 
he suggested
that I send you email explaining the problem and giving you the 
necessary information,
and you could create the access for me by hand.   Please let me know if 
there is
anything else I should do.  Thank you.

Sincerely,
Caroline Tice
ctice@apple.com

First & Last Name:  Caroline Tice
Prefered Login:       ctice
Email Address:       ctice@apple.com
Project:                     gcc
Email address of person who approved request:  geoffk@apple.com

.ssh/id_dsa.pub:  I am attaching the file to prevent cut/paste errors 
in the email system.

[-- Attachment #2: id_dsa.pub --]
[-- Type: application/octet-stream, Size: 612 bytes --]

ssh-dss AAAAB3NzaC1kc3MAAACBAOFKPs4X7NWr68nYQ2oKy3puxc4KMJpUMUMKO04KeB0MNivVk85MF6P632E5v+Nbl32jpTrDoK99D0D33mYiclX7XEHckhKCR9MRrG6Ew/v9T3ixAjHEPQMnjtglW5UYgPD2NKLLo54EEHGFfVXtjP++83SocY9SK3czhVmHhvSFAAAAFQC+ECnyBkzgg0tcxSk5zispdyTvKQAAAIAuo87pIG9WIyA5KH8zuV/QMW5//8b7wBfsrkU+v6UK01CX1lp5IudYGjdAVDUaQO8fZs464XtQG/KtCcK4uAVneXyfixpVV+uGWdsK1efdNGMLy98ksTI2o3oasV97fLNL74UlWNsSC66Sbgdoi1K3lxT1h12GvHBT+i/cC1wLBQAAAIBBkDIuNTnlp8UHhfxYudQeqTT+tPLwEBcZ1WRvzYe9Ik+gftrlqGDTArtwBSTWkmY/E8XSJZCTNzMYY+XogDk7bVNe7aQYWa9yeK26kK8YAsiwHHQcrOWFLwabMWXxpGCIA4bqn9xuBns3nniE6l4OHQLRWT9DzHesUDmNju5YhA== ctice@athena.apple.com

             reply	other threads:[~2003-01-29 22:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 22:13 Caroline Tice [this message]
2003-01-30  9:35 ` Gerald Pfeifer
2003-01-30 15:08   ` Christopher Faylor
2003-01-30 15:26     ` Gerald Pfeifer
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
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=E3D4612D-33D6-11D7-B45C-000393BB90B6@apple.com \
    --to=ctice@apple.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).