All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
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 15:11:34 +0200	[thread overview]
Message-ID: <4CB45E86.2030703@viscovery.net> (raw)
In-Reply-To: <3C33A244-2449-4A3C-A8B5-2060CE61EE04@jetbrains.com>

Am 10/12/2010 14:14, schrieb Kirill Likhodedov:
> 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
> 
> On Mac (and probably on Linux) git inspects the content of MYDIR and
> gives me the status of not-indexed changes in this directory. On
> Windows git gives the same result (only changes in MYDIR), but it scans
> the whole repository!

On Linux, this scans the whole repository, too. Therefore, at least the
Windows version should not be *that* wrong. ;-)

-- Hannes

  parent reply	other threads:[~2010-10-12 13:11 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=4CB45E86.2030703@viscovery.net \
    --to=j.sixt@viscovery.net \
    --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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.