threads / discuss / 58861

git ls-remote windows issue.

Subject: git ls-remote windows issue.

## tl;dr

3 messages between Nov 27, 2022 and Nov 27, 2022.

replies: 2people: 3as markdown or json

Kirill Frolov· Nov 27, 2022, 18:25 UTC · lore

When i run "git ls-remote `origin` HEAD" on windows machine i get "fatal: ''origin'' does not appear to be a git repository"

When i run the same command on same repository on linux machine i get "b7efcb7055a6d45f53c05270a2420aaedaba4d02 HEAD"

rsbecker@nexbridge.com· Nov 27, 2022, 18:38 UTC · re: Kirill Frolov · lore

RE: git ls-remote windows issue.

On November 27, 2022 1:26 PM, Kirill Frolov wrote:

Show 5 quoted lines

>When i run  "git ls-remote `origin` HEAD" on windows machine i get
>"fatal: ''origin'' does not appear to be a git repository"
>
>When i run the same command on same repository on linux machine i get
>"b7efcb7055a6d45f53c05270a2420aaedaba4d02        HEAD"

Try removing the quote characters around origin under Windows. I can reproduce this on Linux using "'origin'", so it appears that the single quotes in your Windows command prompt are being passed in with origin instead of removed as in Linux.

-Randall

Philip Oakley· Nov 27, 2022, 18:48 UTC · re: Kirill Frolov · lore

Re: git ls-remote windows issue.

On 27/11/2022 18:25, Kirill Frolov wrote:

> When i run  "git ls-remote `origin` HEAD" on windows machine i get
> "fatal: ''origin'' does not appear to be a git repository"
>

Are those the right quote marks? Were the commands directly copy/pasted? Note how the report (as received) has back quotes for the command, and then double quoting of ''origin'' on the error resport.

> When i run the same command on same repository on linux machine i get
> "b7efcb7055a6d45f53c05270a2420aaedaba4d02        HEAD"
>
>

-- Philip