Re: ls-files -t broken? Or do I just not understand it?

Björn Steinbrink <B.Steinbrink@gmx.de> writes:

That's not exactly "always", but I don't know whether it's the desired behavior:

/tmp/git$ git st # On branch master # Changed but not updated: # (use "git add/rm <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: modified # deleted: removed # no changes added to commit (use "git add" and/or "git commit -a") /tmp/git$ git ls-files -t H modified H removed H unmodified /tmp/git$ git ls-files -t -m C modified C removed /tmp/git$ git ls-files -t -d R removed $ git ls-files -t -d -m C modified R removed C removed

So, you get the C and R flags only when you request explicitely -m and -d.

I'd say this is a bug, and anyway a testcase should be added to explicitly state what the behavior should be.