Re: [PATCH] git-revert is one of the most misunderstood command in git, help users out.

Hi,

On Wed, 7 Nov 2007, Mike Hommey wrote:

On Tue, Nov 06, 2007 at 10:25:48PM +0000, Johannes Schindelin [off-list ref] wrote:

quoted

On Tue, 6 Nov 2007, Robin Rosenberg wrote:

quoted

tisdag 06 november 2007 skrev Mike Hommey:

quoted

Maybe the documentation could emphasise on how to undo things when 
the user makes mistakes. Sometimes, saving your repo can be as 
simple as git reset --hard HEAD@{1}. This is not, unfortunately, a 
works-for-all-cases command.

Yea, git-undo(7). 

In related news, I know a few users who need an un-rm-rf.  Anyone?

The fact is you can do harm to your repo with things you wouldn't expect 
to break things, except maybe you gave bad arguments or so. It's quite 
easy to fuck up with git-rebase, or to merge the wrong commits, etc.

I don't see how these commands are dangerous.  Usually you just look into 
the reflog, pick the one commit you started with, and reset --hard.

The _only_ commands I find dangerous are "git stash clear" and "git reflog 
--expire=0".  Funnily, people want to do that all the time.

Like recently, on the IRC channel, where somebody lost patches "during a 
rebase", by "rm -rf .dotest".

There will be a point where nobody can help.  But before that, reflogs are 
your friend.  But you must not do "reset --hard HEAD@{1}" blindly.  You 
have to look first what the reflogs are.

Ciao,
Dscho