From: Junio C Hamano <gitster@pobox.com>
To: "Joe Casadonte" <jcasadonte@northbound-train.com>
Cc: git@vger.kernel.org
Subject: Re: git clone - failing on cygwin with git:// but not with ssh://
Date: Tue, 30 Dec 2008 11:54:29 -0800 [thread overview]
Message-ID: <7v1vvp30cq.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <u7i5hy5ti.fsf@terrapin.northbound-train.com> (Joe Casadonte's message of "Tue, 30 Dec 2008 11:40:41 -0500")
"Joe Casadonte" <jcasadonte@northbound-train.com> writes:
> Looking for a little help, please. Is this not a legitimate git issue? Can
> anyone at least help me diagnose the issue? Please?
I think "git on Cygwin" is as legitimate as git on anything else, but at
the same time my guess is that it is a combination of the fact that
everybody is busy with other things around the end of year , and that
probably there are not many "git on Cygwin" experts monitoring the list to
begin with.
Sorry, I do not work on Cygwin (nor Windows in general). "fatal: read
error (Socket operation on non-socket)" sounds like it is coming from
pkt-line.c::safe_read() on the downloading side (i.e. git-clone).
Googling for that error message seems to indicate that it seems to a
rather common error message on wide variety of programs running on Cygwin.
C.f.
http://www.google.com/search?&q=%22Socket+operation+on+non-socket%22+site%3Acygwin.com
next prev parent reply other threads:[~2008-12-30 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 16:40 git clone - failing on cygwin with git:// but not with ssh:// Joe Casadonte
2008-12-30 19:54 ` Junio C Hamano [this message]
2008-12-30 20:01 ` Joe Casadonte
-- strict thread matches above, loose matches on Subject: below --
2008-12-27 22:37 Joe Casadonte
2008-12-29 14:54 ` Joe Casadonte
2008-12-30 23:52 ` Daniel Barkalow
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=7v1vvp30cq.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jcasadonte@northbound-train.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 NNTP newsgroup(s).