git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Kirill Likhodedov <Kirill.Likhodedov@jetbrains.com>
Cc: git@vger.kernel.org
Subject: Re: git ls-files handles paths differently in Windows and Mac (probably Linux)
Date: Tue, 12 Oct 2010 14:51:05 +0200	[thread overview]
Message-ID: <AANLkTimB6s_yt6L59xpqsWO_yBsZxuVCiExFoSm9FcN1@mail.gmail.com> (raw)
In-Reply-To: <3C33A244-2449-4A3C-A8B5-2060CE61EE04@jetbrains.com>

On Tue, Oct 12, 2010 at 14:14, Kirill Likhodedov
<Kirill.Likhodedov@jetbrains.com> wrote:
> The behavior of ls-files is inconsistent in Windows and Mac.
>
> I want to see which files were changed in the specific directory of my working tree, so I call ls-files:
>> git ls-files -douvm --exclude-standard -- MYDIR
>

Well, it is an... unconventional way to do that. May I suggest you consider
using "git diff --name-status" or just "git status" next time?

> Looks like a bug. Maybe a bug of porting Git to windows, but the behavior is the same on msys-git and cygwin-git.

Maybe. Both ports share a fair amount of Windows-related code.

  reply	other threads:[~2010-10-12 12:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 12:14 git ls-files handles paths differently in Windows and Mac (probably Linux) Kirill Likhodedov
2010-10-12 12:51 ` Alex Riesen [this message]
2010-10-12 12:59   ` Kirill Likhodedov
2010-10-12 13:52     ` Kirill Likhodedov
2010-10-12 15:25       ` Alex Riesen
2010-10-13  9:09         ` Kirill Likhodedov
2010-10-13 10:35           ` Alex Riesen
2010-10-13 11:20           ` Jakub Narebski
2010-10-13 11:35             ` Kirill Likhodedov
2010-10-12 15:24     ` Alex Riesen
2010-10-12 13:11 ` Johannes Sixt
2010-10-12 13:24   ` Kirill Likhodedov
2010-10-12 13:28     ` Johannes Sixt

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=AANLkTimB6s_yt6L59xpqsWO_yBsZxuVCiExFoSm9FcN1@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=Kirill.Likhodedov@jetbrains.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).