git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Packham <judge.packham@gmail.com>
To: Erik Friesen <erik@aercon.net>
Cc: GIT <git@vger.kernel.org>, msysgit@googlegroups.com
Subject: Re: Windows Bluescreen
Date: Thu, 12 Feb 2015 22:33:18 +1300	[thread overview]
Message-ID: <CAFOYHZAMv5BEmDXGSoo53iSwCYLdhOcM7dHwCMidZBaJh0xmUQ@mail.gmail.com> (raw)
In-Reply-To: <CAEuupitA4PHBByLLcqc5pVbn1C+ZyQ6Vzbk-LsOjseOEHhkENw@mail.gmail.com>

On Thu, Feb 12, 2015 at 1:33 AM, Erik Friesen <erik@aercon.net> wrote:
> Pushing over http and https are unaffected..  My linux nas died, so on
> rebuild I tried to do the ssh thing, and realized quite soon that
> things weren't right.
>
> As far as other uses of ssh, I don't know, I use putty frequently, but
> I am not clear if it is using the same libraries or not.

I think putty ships it's own ssh implementation rather than using an
openSSH port.

> I hunted around for the bugreport email on mysgit but couldn't seem to
> find it.  It seems in the foggy recesses I remember reading about an
> ssh issue with windows, but can't find it now.
>

https://github.com/msysgit/git/issues

Happy hunting :). Actually if it is a ssh problem it might be a
generic MSYS issue. So there's another bug tracker to look through

http://sourceforge.net/p/mingw/bugs/


> On Wed, Feb 11, 2015 at 3:56 AM, Chris Packham <judge.packham@gmail.com> wrote:
>> Hi Erik,
>>
>> On Tue, Feb 10, 2015 at 9:12 AM,  <erik@aercon.net> wrote:
>>>
>>> I find that preview 1.8 is bluescreening on about 1 of 3 ssh pushes.  1.9
>>> preview 12-17-2014 doesn't even bluescreen, the windows gui locks until
>>> reset.
>>
>> Does this mean that pushing over git:// file:// and http:// are
>> unaffected? Can you successfully do other (non-git) things over ssh?
>>
>>>
>>> Sample command:
>>> git push omv master\r
>>>
>>> config. =
>>>
>>> [core]
>>>         repositoryformatversion = 0
>>>         filemode = false
>>>         bare = false
>>>         logallrefupdates = true
>>>         symlinks = false
>>>         ignorecase = true
>>>         hideDotFiles = dotGitOnly
>>> [remote "omv"]
>>>         url = gitpush@192.168.0.100:/git-repos/HexEncrypter
>>>         fetch = +refs/heads/*:refs/remotes/omv/*
>>>
>>
>> You might get a more helpful response out of the msysgit folks (I've
>> added them to the Cc list).

-- 
-- 
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.

You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups "Git for Windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2015-02-12  9:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 20:12 Windows Bluescreen erik
2015-02-11  8:56 ` Chris Packham
2015-02-11 12:33   ` Erik Friesen
2015-02-12  9:33     ` Chris Packham [this message]
2015-02-12 12:21       ` Erik Friesen
2015-02-12 12:25         ` Erik Friesen
2015-02-12 12:42         ` Thomas Braun
2015-02-12 13:21           ` Erik Friesen
2015-02-12 13:48             ` Yue Lin Ho
2015-02-13 21:09             ` Thomas Braun
2015-02-12 12:53         ` Jason Pyeron

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=CAFOYHZAMv5BEmDXGSoo53iSwCYLdhOcM7dHwCMidZBaJh0xmUQ@mail.gmail.com \
    --to=judge.packham@gmail.com \
    --cc=erik@aercon.net \
    --cc=git@vger.kernel.org \
    --cc=msysgit@googlegroups.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).