From: Bill Hoffman <bill.hoffman@kitware.com>
To: cygwin@cygwin.com, jeremy@bopp.net
Subject: Re: git and openssh issue
Date: Thu, 22 Jul 2010 19:49:00 -0000 [thread overview]
Message-ID: <4C48A06F.6020309@kitware.com> (raw)
In-Reply-To: <4C4862F6.7090602@bopp.net>
On 7/22/2010 11:25 AM, Jeremy Bopp wrote:
>>
>> Are there any other experiments you would like to see? Seems to happen
>> with any reasonable size git repo. So, if you were to say clone VTK or
>> Qt, I am sure you could reproduce this as well.
>
> I'm game to try this out. Can you send me the exact git command you use
> to clone one or more of these repositories so that I can try to
> reproduce what you see?
>
> -Jeremy
>
We have reproduced this with the CMake git repo. You can find out how
to get a clone of that here:
http://www.cmake.org/Wiki/CMake/Git
So to clone CMake do this:
git clone git://cmake.org/cmake.git CMake
Once you clone CMake to a machine, you can then clone from that machine
like this:
Commands for ssh clone:
$ git clone user@machine:path/to/repo.git
Commands for rsh clone:
$ echo '#!/bin/sh
exec rsh -l user "$@"' > ~/ssh-rsh
$ chmod 750 ~/ssh-rsh
$ GIT_SSH=~/ssh-rsh git clone machine:path/to/repo.git
Commands for plink clone:
http://my.afterdawn.com/agent_007/blog_entry.cfm/2909/git_and_cygwin
One thing that might be a good thing to try is to bisect the openssh
source. That might eliminate the cygwin dll as the source of the
problem. Or at least find out which change in openssh caused the problem.
-Bill
--
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:[~2010-07-22 19:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 17:15 Bill Hoffman
2010-07-21 5:48 ` Jeremy Bopp
2010-07-22 15:22 ` Bill Hoffman
2010-07-22 15:49 ` Jeremy Bopp
2010-07-22 19:49 ` Bill Hoffman [this message]
2010-07-22 23:48 ` Jeremy Bopp
2010-07-23 1:53 ` Bill Hoffman
2010-07-23 16:28 ` Jeremy Bopp
2010-07-23 17:01 ` git and openssh issue (eblake?) Christopher Faylor
2010-08-02 14:08 ` Bill Hoffman
2010-08-12 13:46 ` Bill Hoffman
2010-10-03 2:54 ` Christopher Faylor
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=4C48A06F.6020309@kitware.com \
--to=bill.hoffman@kitware.com \
--cc=cygwin@cygwin.com \
--cc=jeremy@bopp.net \
/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).