mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Sixt <>
To: Alexandre Remy <>
Subject: Re: Git pathspecs difference in behavior between linux (wsl) and windows
Date: Thu, 13 May 2021 09:49:05 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Am 13.05.21 um 08:57 schrieb Alexandre Remy:
> Hi,
> I do not understand why the same command works on linux and not on
> windows. Is the pathspecs syntax differ or there is a problem on the
> git windows version?
> * On windows (git version
> git status -- 'src/test.js'
> On branch master
> nothing to commit, working tree clean
> * On linux (wsl: git version 2.25.1)
> git status -- 'src/test.js'
> On branch master
> Changes not staged for commit:
>   (use "git add <file>..." to update what will be committed)
>   (use "git restore <file>..." to discard changes in working directory)
>         modified:   src/test.js
> A classic git status gives the same result between linux and windows
> (with correct file detected).

Which shell did you use to invoke the Windows version? If it was from
CMD or PowerShell, then you must not put the name in single-quotes:

   git status -- src/test.js

The reason is that the single-quote does not have a special meaning for
CMD and PowerShell like it does for a POSIX shell.

-- Hannes

  reply	other threads:[~2021-05-13  7:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13  6:57 Git pathspecs difference in behavior between linux (wsl) and windows Alexandre Remy
2021-05-13  7:49 ` Johannes Sixt [this message]
2021-05-13  8:05   ` Alexandre Remy
2021-05-13  9:31     ` Alexandre Remy
2021-05-13 13:02       ` Johannes Sixt
2021-05-13 20:08         ` Junio C Hamano
2021-05-13 21:03           ` Johannes Sixt
2021-05-13 21:17             ` Alexandre Remy

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).