From: Väinö Järvelä <v@pp.inet.fi>
Date: Fri, 24 Aug 2007 06:35:13 GMT
Subject: Re: [PATCH 1/2] Add "--only-untracked" flag to status commands.
Message-ID: <6D8BA2E0-50CD-4B7B-84D3-3D9A61421131@pp.inet.fi>
In-Reply-To: <20070823203246.GB3516@steel.home>

On Aug 23, 2007, at 23:32, Alex Riesen wrote:

> Väinö Järvelä, Thu, Aug 23, 2007 21:58:31 +0200:
>> With this flag, the user can choose to filter untracked files from  
>> the
>> status output. This can be used to either speed up the status  
>> output, as
>> the untracked files are not fetched at all, or to just cleanup the
>> output without using gitignore.
>
> "git diff -r --name-status; git diff --cached -r --name-status" is  
> not enough?

That line will result in duplicate entries, if files are staged, and  
the output of git-status is neater (but longer) in my opinion.

"""
M       Makefile
M       Makefile
"""
vs.
"""
# On branch entity_class
# Changes to be committed:
#   (use "git reset HEAD <file>..." to unstage)
#
#       modified:   Makefile
#
# Changed but not updated:
#   (use "git add <file>..." to update what will be committed)
#
#       modified:   Makefile
#
# Untracked files were filtered by "--only-tracked"
"""

Sure you could remove duplicate entries with "sort|uniq", or  
something, but just running "git status --only-tracked", is cleaner,  
and more user friendly.

The way I see the flag used is: A user runs "git status", sees that  
there is too much untracked files and not enough scrollback, so he  
runs "git status --only-tracked" to filter the results.

--
Väinö