On Sun, Feb 19, 2006 at 09:42:16PM +0100, Wolfgang Denk wrote:
In message 20060219184252.GA8860@mars.ravnborg.org you wrote:
git ls-files -o does a better job identifying stale files.
Maybe. But I did not talk about stale files.
git status is useful during a normal development practice where you do
Define "normal". It seems to mean different things for you and me.
Consider you add a new driver to u-boot. This includes modifying top-lvel README, a Makefile and you add two new files.
If all files created during a build are included in .gitignore files then if you issue: 'git status' at any point in time (no need to run mrproper) you will get an overview over: - modified files - new files (listed as untracked files) and more importanly the git status output is not cluttered with a lot of 'build noise'.
If you then like to check the properness of make mrproper you issue 'make mrproper' and then what was not cleaned by 'make mrproper' shows up with 'git ls-files-o'.
Hope this clarified my comment.
Sam