> From: Pierre-François CLEMENT <lik...@gmail.com>

> Ah, my mistake I've misread you in the first place. You're right, it feels
> natural they should return to their "untracked" state rather than being
> deleted. And it sounds definitely possible to implement: git could just
> check if the file was tracked or not before deleting it, the same way it
> can tell the file has been "added" or "modified".

Beware, though.  I don't have my Git reference to hand, but I've noted
that if the file is in the index, it is "tracked" and the git-reset
manual page says:

               Resets the index and working tree. Any changes to tracked files
               in the working tree since <commit> are discarded.

What you want is an exception for files that are in the index but
*not* in the base commit.  Or perhaps the criterion should be "files
that are in the commit", rather than "tracked files".


You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to