PowerShell / PowerShell/Win32-OpenSSH
git clone always give error message,fatal: ''mongodb'' does not appear to be a git repository, with a wired double quotes
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
$ git clone ssh://gitbk@192.168.2.100:mongodb
Cloning into 'mongodb'...
gitbk@192.168.2.100's password:
fatal: ''mongodb'' does not appear to be a git repository ---------------this is the wrong output of git-upload pack, git clone will call the git-upload-pack in remote server
fatal: Could not read from remote repository.
BUT I TRIED THIS ,IT WORKS
$ ssh gitbk@192.168.2.100 "git-upload-pack mongodb"
gitbk@192.168.2.100's password:
0000----------------this is a right ouput is git-upload-pack
I found instead of single quotes of ''mongodb''in err msg ---fatal: ''mongodb'' does not appear to be a git repository---, gives a wired double quotes, and I tried in local the 'git-upload-pack' command, it only give single quote in its err msg.
I think something wrong when transferring the repo path to ssh remote server, shoud be caused by the openssh
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with the shown git clone command and compare it with the direct ssh git-upload-pack invocation. Trace how the remote repository path is transferred and quoted for the SSH command, then verify that git clone produces the same repository-path handling without doubled quotes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100