From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] cygport upload
Date: Fri, 13 Feb 2015 04:10:00 -0000 [thread overview]
Message-ID: <1423800617.12472.192.camel@cygwin.com> (raw)
In-Reply-To: <ifkqdatllqs13avpnaas8dr59c4jv2ugj6@4ax.com>
On Thu, 2015-02-12 at 20:23 -0500, Andrew Schulman wrote:
> > I have created an upload branch in cygport git based on master with
> > Andrew's upload work for further testing.
>
> FWIW, I've been using it to upload my packages since the last update on Jan. 17,
> and before that too, with no problems.
>
> I always keep my ssh keys loaded in a running ssh-agent, so I've tested that
> case pretty well. I think it would be most useful to test the other cases:
> ssh-agent running but key not loaded; ssh-agent not running; private keys
> encrypted/unencrypted.
I am testing it both with an ssh-agent (gnome-keyring) and without, and
my keys are encrypted.
--
Yaakov
prev parent reply other threads:[~2015-02-13 4:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 22:42 Yaakov Selkowitz
2015-02-12 22:51 ` Marco Atzeri
2015-02-13 0:28 ` Yaakov Selkowitz
2015-02-13 1:00 ` Andrew Schulman
2015-02-13 1:23 ` Andrew Schulman
2015-02-13 4:10 ` Yaakov Selkowitz [this message]
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=1423800617.12472.192.camel@cygwin.com \
--to=yselkowitz@cygwin.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).