git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Konstantin Khomoutov'" <kostix@bswap.ru>,
	"'Luis Heredia'" <luis.heredia@tool.es>
Cc: <git@vger.kernel.org>
Subject: RE: Git problem in windows server
Date: Thu, 21 Nov 2024 14:28:34 -0500	[thread overview]
Message-ID: <035401db3c4b$91ca9c70$b55fd550$@nexbridge.com> (raw)
In-Reply-To: <20241121190522.6s63bsvhxm3w5f5b@carbon>

On November 21, 2024 2:05 PM, Konstantin Khomoutov wrote:
>On Thu, Nov 21, 2024 at 11:24:42AM +0100, Luis Heredia wrote:
>
>[...]
>> The problem is when i try to clone in my windows 10 local machine (cmd
>> git clone - v ssh://user@serverIp:port/gitServer/git.git c:/temp) i
>> always receive the error "fatal: ´´/gitServer/git.git''  does not
>> appear to be a git repository".
>
>Does it work if you call
>
>  git clone ssh://user@serverIp:port/c/gitServer/git.git
>
>or may be
>
>  git clone ssh://user@serverIp:port/c:/gitServer/git.git
>
>?
>
>Basically the problem appears to be in that the Git process spawned
remotely in the
>SSH session set up by your local Git process, is given the path component
of the
>repository URL, which is "/gitServer/git.git" in your case.
>Obviously, this path is not correct on Windows filesystems.

Some SSH servers restrict interactions to a specific directory rather than
allowing access
to the root of the disk. I got around that by setting up a link (via
Cygwin64) to the target
location, which bypasses the configured SSH root. It would then require a
different
URI to account for that.

--Randall


  reply	other threads:[~2024-11-21 19:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 10:24 Git problem in windows server Luis Heredia
2024-11-21 14:28 ` Phillip Wood
2024-11-21 19:05 ` Konstantin Khomoutov
2024-11-21 19:28   ` rsbecker [this message]
2024-11-22 10:03 ` Konstantin Khomoutov

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='035401db3c4b$91ca9c70$b55fd550$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=kostix@bswap.ru \
    --cc=luis.heredia@tool.es \
    /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).