RE: Suggestion: make git checkout safer

From: Randall S. Becker <rsbecker@nexbridge.com>
Date: Jun 3, 2015, 18:18 UTC
Message-ID: <004901d09e29$b38c2ba0$1aa482e0$@nexbridge.com>
In-Reply-To: <xmqq4mmoy84y.fsf@gitster.dls.corp.google.com>

On June 3, 2015 2:11 PM Junio C Hamano wrote:

Show 18 quoted lines

> "Randall S. Becker" <rsbecker@nexbridge.com> writes:
> > On June 3, 2015 1:35 PM Junio C Hamano wrote:
> >> Is that really true?  It all depends on why you came to a situation
> >> to have "missing files" in the first place, I would think, but "git
> >> checkout $path" is "I messed up the version in the working tree at
> >> $path, and want to restore them".  One particular kind of "I messed
> >> up" may be "I deleted by mistake"
> >> (hence making them "missing"), but is it so common to delete things
> >> by mistake, as opposed to editing, making a mess and realizing that
> >> the work so far was not improving things and wanting to restart from
> >> scratch?
> >
> > When working in an IDE like ECLIPSE or MonoDevelop, accidentally
> > hitting the DEL button or a drag-drop move is a fairly common trigger
> > for the "Wait-No-Stop-Oh-Drats" process which includes running git
> > checkout to recover.
> 
> That is an interesting tangent.  If you are lucky then the deleted file

may be

> unedited one, but I presume that you are not always lucky.  So perhaps

"git

> checkout" is not a solution to that particular IDE issue in the first

place?

Agreed. That's why I like knowing what's in my sausages and commit often. Only lost a minor change once from this. I wonder what else is afoot. Ed, can you expand on the issue?