From: Jeff Whiteside <jeff.m.whiteside@gmail.com>
Date: Thu, 11 Sep 2008 23:04:19 GMT
Subject: Re: RFC: perhaps a "new file" should not be deleted by "git reset --hard"
Message-ID: <3ab397d0809111604r5d9dda04p32a987208d1fa92d@mail.gmail.com>
In-Reply-To: <279b37b20809111519o76bea81br738983b4cda1978e@mail.gmail.com>

The command is wrapped up in all kinds of semantics at which you have
to guess or read tons of vague or outdated literature.  That's what
makes git's learning curve so retarded.

Why is it not just    git reset --index     or     git reset
--worktree    or   git reset --commitrepo REVISION  or   git reset
--all ?
And if you want to delete all untracked files
     ls | sed s/`git status --index --filenamesonly`//g | rm
     ls | sed s/`git status --commitrepo --filenamesonly`//g | rm
           (I realize those commands don't actually work, but I'm a noob.)

So that 'tracked by git' isn't just another ambiguous semantic.
Instead 'Tracked by index'/'Tracked by commitrepo'.