git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Matthias Fechner <idefix@fechner.net>
Cc: git@vger.kernel.org
Subject: Re: Cannot push a commit
Date: Wed, 18 Jan 2012 18:09:14 -0800	[thread overview]
Message-ID: <20120119020913.GA20219@sigill.intra.peff.net> (raw)
In-Reply-To: <4F170E7E.9000804@fechner.net>

On Wed, Jan 18, 2012 at 07:25:02PM +0100, Matthias Fechner wrote:

> Am 17.01.2012 08:35, schrieb Matthias Fechner:
> > So the problem has something to do with windows as client. I will do
> > some additional test this evening.
> > 
> > Where can we continue to search?
> [...]
> Then I opened the git bash and inserted:
> export GIT_SSH=plink.exe
> git push
> [...]

Thanks for following up on this. It does seem like openssh is dropping
your connection in a half-duplex way, though we don't know why. A bug in
openssh sounds like a reasonable candidate...

> The currently installed version is OpenSSH_4.6p1, OpenSSL 0.9.8e 23
> Feb 2007.  Maybe an updated openssh version in the git bin folder will
> solve the problem?

Especially given how old your version is. Certainly I would try with a
more recent version. If it clears up the problem, I'm willing to assume
it's an openssh bug that's been fixed. If it doesn't, then it may be an
open openssh bug, or perhaps there is some problem in the way we're
invoking it on Windows. We can investigate that path if need be.

-Peff

  reply	other threads:[~2012-01-19  2:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15  9:09 Cannot push a commit Matthias Fechner
2012-01-16 18:59 ` Matthias Fechner
2012-01-16 21:20 ` Jeff King
2012-01-17  7:35   ` Matthias Fechner
2012-01-18 18:25     ` Matthias Fechner
2012-01-19  2:09       ` Jeff King [this message]
2012-01-24  6:53         ` Matthias Fechner

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=20120119020913.GA20219@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=idefix@fechner.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 NNTP newsgroup(s).