From: Mark Geisert <mark@maxrnd.com>
To: cygwin-apps@cygwin.com
Subject: Re: Still unable to 'git push' or ssh to sourceware
Date: Tue, 10 Nov 2015 05:03:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.63.1511092100310.864@m0.truegem.net> (raw)
In-Reply-To: <1447130862.11732.16.camel@cygwin.com>
On Mon, 9 Nov 2015, Yaakov Selkowitz wrote:
> On Mon, 2015-11-09 at 17:54 -0800, Mark Geisert wrote:
>> I had assumed that having sent my "SSH key for upload access", it goes to
>> the same location as my original key supplied on the
>> sourceware.org/cgi-bin/pdw/ps_form.cgi form.
>
> Incorrect. Upload access is completely separate from shell access to
> sourceware, and neither implies or requires the other.
Thanks for that. I need to update my shell access key but I can't make
use of the appendkey trick, catch-22. Sounds like I should contact
overseers then.
..mark
next prev parent reply other threads:[~2015-11-10 5:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 1:54 Mark Geisert
2015-11-10 4:47 ` Yaakov Selkowitz
2015-11-10 5:03 ` Mark Geisert [this message]
2015-11-10 9:21 ` Corinna Vinschen
2015-11-12 9:22 ` Still unable to 'git push' or ssh to sourceware -- resolved Mark Geisert
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=Pine.BSF.4.63.1511092100310.864@m0.truegem.net \
--to=mark@maxrnd.com \
--cc=cygwin-apps@cygwin.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).