From: Ryan Johnson <ryanjohn@ece.cmu.edu>
To: cygwin@cygwin.com
Subject: Re: Mercurial not returning with 20110601 snapshot
Date: Thu, 02 Jun 2011 13:34:00 -0000 [thread overview]
Message-ID: <4DE7915E.3020801@ece.cmu.edu> (raw)
In-Reply-To: <BANLkTim7+mG41OifRJnx0S4JxMWc+scMRA@mail.gmail.com>
On 02/06/2011 9:05 AM, Chris Sutcliffe wrote:
> On 2 June 2011 08:27, Christopher Faylor wrote:
>> Could you provide the actual steps needed to duplicate the problem,
>> assuming that anyone doing testing will not be familiar with mercurial?
> It seems to be an issue with using mercurial over ssh versus mercurial
> over http. For example, cloning the Emerge Desktop repository over
> http (read only) works fine:
>
> hg clone http://emerge.hg.sourceforge.net:8000/hgroot/emerge/emerge
>
> However, when I clone over ssh (for read/write) using my public key:
>
> hg clone ssh://ir0nh34d@emerge.hg.sourceforge.net/hgroot/emerge/emerge
>
> The command appears to hang after the operation completes.
>
> Unfortunately I don't know of an anonymous mercurial repository that
> you can clone over ssh to recreate the issue.
Assuming cygwin sshd is running locally, couldn't you just create an
empty repo and then try to ssh-clone it?
mkdir ~/test-repo
cd ~/test-repo
hg init
hg clone ssh://localhost/test-repo tr2
Ryan
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-06-02 13:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 10:44 Chris Sutcliffe
2011-06-02 12:28 ` Christopher Faylor
2011-06-02 13:06 ` Chris Sutcliffe
2011-06-02 13:34 ` Ryan Johnson [this message]
2011-06-02 13:46 ` marco atzeri
2011-06-02 15:48 ` Chris Sutcliffe
2011-06-03 2:25 ` Christopher Faylor
2011-06-03 3:32 ` Ryan Johnson
2011-06-04 1:14 ` Christopher Faylor
2011-06-04 1:57 ` Chris Sutcliffe
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=4DE7915E.3020801@ece.cmu.edu \
--to=ryanjohn@ece.cmu.edu \
--cc=cygwin@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).