From: Erik Cervin Edin <erik@cervined.in>
To: "W. Ekkehard Blanz" <ekkehard.blanz@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Cloning remotely under git for Windows not working
Date: Thu, 20 Oct 2022 22:29:56 +0200 [thread overview]
Message-ID: <CA+JQ7M_hE66XiBc4G7nXJMWpdOBWEm+Zp_74LcXQSOD8fo9LJw@mail.gmail.com> (raw)
In-Reply-To: <CA+JQ7M-NA9UYafMurb9MAo5bp6djdzRP7ChAbdmzU+nmrkXTNw@mail.gmail.com>
sorry, forgot reply all
On Thu, Oct 20, 2022 at 6:04 PM W. Ekkehard Blanz
<ekkehard.blanz@gmail.com> wrote:
>
> $ git clone 10.0.7.181:D:\gitDepot\test.git
> Cloning into 'test'...
> username@10.0.7.181's password:
> fatal: ''D:\gitDepot\test.git'' does not appear to be a git repository
> fatal: Could not read from remote repository.
Any interesting information if you run with
GIT_TRACE=1 git clone ...
or any of the other debugging flags?
https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables
I recall having a difficult time when I hosted a repository on windows
a while back. Not exact specifics but that I ran into issues. Maybe
because of some default windows things. Like the default terminal
and/or the default ssh client.
Maybe something along the lines in this stackoverflow post
https://stackoverflow.com/a/67937630/1507124
It mentions the following issue
https://github.com/PowerShell/Win32-OpenSSH/issues/752
and the workaround is setting receive/uploadpack to use powershell.
I distinctly recall facing this issue and I believe I solved it the
same way, changing the default ssh shell to PowerShell instead of cmd.
Not sure if it solves your issue but I think it helped me.
I'm also pretty sure that another time I tried setting mingw-bash as
the ssh shell and then faced another issue related to mingw/windows
path quoting shenanigans
next prev parent reply other threads:[~2022-10-20 20:30 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 [this message]
[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
-- 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_hE66XiBc4G7nXJMWpdOBWEm+Zp_74LcXQSOD8fo9LJw@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).