Re: [PATCH 2/2] read-tree: at least one tree-ish argument is required

Heya,

On Fri, Dec 18, 2009 at 13:49, Junio C Hamano [off-list ref] wrote:

You might type
"commit" when you meant to say "commit -a" and record an incomplete state;
it is "dangerous" in that sense.

Speaking of which, it has hit me multiple times that I craft out a
commit with 'git add -p' and then do "git commit -am 'foo some bars'"
and lose all my hard work (because I'm used to typing 'git commit -am'
for temporary commits). I'd be happy if "git commit -am" learned to
second-guess me when I already have something in the index.

These are part of their feature.

Fair enough, then perhaps it is time for "core.nodataloss" which
either logs states to a seperate reflog (so that you can go back to
the state you were in before doing 'git read-tree') or interactively
informs the user that this will command will result in data loss
(although that sounds a tad too much like Window's "Are you sure?"
dialogs).

-- 
Cheers,

Sverre Rabbelier