On Thu, Sep 11, 2008 at 4:39 PM, Miklos Vajna <vmiklos@xxxxxxxxxxxxxx> wrote: > On Thu, Sep 11, 2008 at 02:24:51PM -0700, Eric Raible <raible@xxxxxxxxx> wrote: >> My question is why "git reset --hard" can't make a special case for >> _newly added_ tracked files. After all, "git status" knows that they're >> "new files", and "git reset --hard" could realize that wiping them off >> the face of the earth isn't the most helpful thing possible. > > I rarely need this, but I use 'git read-tree -m HEAD' before git reset > --hard in case I want such a behaviour. What advantages does "git read-tree -m HEAD" have over "git reset" or "git rm --cached <file list>"? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
