git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Cervin Edin <erik@cervined.in>
To: "W. Ekkehard Blanz" <ekkehard.blanz@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Cloning remotely under git for Windows not working
Date: Fri, 21 Oct 2022 08:09:23 +0200	[thread overview]
Message-ID: <CA+JQ7M-Brkq1xwcNhQ+rTvtbtR-XpHspTPJ8kXA63fLxarez_g@mail.gmail.com> (raw)
In-Reply-To: <46A1CB40-BBEE-43FC-9626-588718518B4A@gmail.com>

On Fri, Oct 21, 2022 at 12:00 AM W. Ekkehard Blanz
<ekkehard.blanz@gmail.com> wrote:
>
> Regarding your suggestion re. Powershell, I can start the cloning command in a power shell window on a different (or the same) Windows box, no problem, but this gives me the same result.

Sorry maybe I should have been clearer but the powershell part is only
relevant on the remote. ie, the remote shell. CMD and windows OpenSSH
on the remote are the culprit in the issue I've mentioned

  parent reply	other threads:[~2022-10-21  6:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 15:58 Cloning remotely under git for Windows not working W. Ekkehard Blanz
2022-10-20 17:24 ` Torsten Bögershausen
     [not found]   ` <5F48868F-1788-4BB6-8E24-1652B919B60E@gmail.com>
2022-10-20 20:50     ` W. Ekkehard Blanz
     [not found] ` <CA+JQ7M-NA9UYafMurb9MAo5bp6djdzRP7ChAbdmzU+nmrkXTNw@mail.gmail.com>
2022-10-20 20:29   ` Erik Cervin Edin
     [not found]   ` <DB5611E0-6B1C-4711-BB9F-72F6E8F39506@gmail.com>
2022-10-20 20:31     ` Erik Cervin Edin
2022-10-20 21:58       ` W. Ekkehard Blanz
2022-10-21  6:06         ` Erik Cervin Edin
2022-10-22  0:05           ` W. Ekkehard Blanz
2022-10-21  6:09         ` Erik Cervin Edin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-20 15:48 W. Ekkehard Blanz

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=CA+JQ7M-Brkq1xwcNhQ+rTvtbtR-XpHspTPJ8kXA63fLxarez_g@mail.gmail.com \
    --to=erik@cervined.in \
    --cc=ekkehard.blanz@gmail.com \
    --cc=git@vger.kernel.org \
    /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).