From: Radoslaw Szkodzinski <astralstorm@o2.pl>
To: git@vger.kernel.org
Subject: Question about git-ls-files
Date: Fri, 24 Mar 2006 23:49:47 +0100 [thread overview]
Message-ID: <200603242349.54578.astralstorm@o2.pl> (raw)
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
git-ls-files is a very useful command to list various types of files.
However, it has some weird behaviour.
Let's say someone removed the file and not updated the index yet.
I want to get status for all files in the directory, so I launch git-ls-files
-t -m -d -o, and I get:
R removed-file
C removed-file
? something-else
(it looks even better if I call it w/o -t)
If the file is removed, then marking it as changed is redundant.
A removed file cannot be unchanged.
This behaviour makes for slow parsing, because to get the changed files which
still exist one has to at least skip items (or uniquify the list). This
shouldn't be needed.
Removed files should of course still be listed as changed if there's no -d
parameter.
--
GPG Key id: 0xD1F10BA2
Fingerprint: 96E2 304A B9C4 949A 10A0 9105 9543 0453 D1F1 0BA2
AstralStorm
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
reply other threads:[~2006-03-24 22:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200603242349.54578.astralstorm@o2.pl \
--to=astralstorm@o2.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox