All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: "'Ed Avis'" <eda@waniasset.com>, <git@vger.kernel.org>
Subject: Re: Suggestion: make git checkout safer
Date: Wed, 03 Jun 2015 11:11:25 -0700	[thread overview]
Message-ID: <xmqq4mmoy84y.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <004801d09e25$a339b0f0$e9ad12d0$@nexbridge.com> (Randall S. Becker's message of "Wed, 3 Jun 2015 13:49:27 -0400")

"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?

  reply	other threads:[~2015-06-03 18:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  8:50 Suggestion: make git checkout safer Ed Avis
2015-06-03  9:06 ` Jeff King
2015-06-03  9:21   ` Ed Avis
2015-06-03  9:35     ` Jeff King
2015-06-03  9:55       ` Ed Avis
2015-06-03 17:35         ` Junio C Hamano
2015-06-03 17:49           ` Randall S. Becker
2015-06-03 18:11             ` Junio C Hamano [this message]
2015-06-03 18:18               ` Randall S. Becker
2015-06-03 18:14             ` Stefan Beller
2015-06-04 10:47               ` Ed Avis
2015-06-04 11:02                 ` Ed Avis
2015-06-03 19:26         ` Torsten Bögershausen
2015-06-03 19:47         ` Kevin Daudt
2015-06-04 11:00           ` Ed Avis
2015-06-04 20:14             ` Torsten Bögershausen
2015-06-05  9:32               ` Ed Avis
2015-06-05 10:49                 ` Duy Nguyen
2015-06-05 17:44                 ` Eric Sunshine
2015-06-05 18:03                   ` Junio C Hamano
2015-06-05 18:46                     ` Ed Avis
2015-06-05 18:37                   ` Eric Sunshine
2015-06-03 20:12         ` Philip Oakley
2015-06-03 17:32       ` Junio C Hamano
2015-06-03 19:06         ` Jeff King
2015-06-03 19:24           ` Randall S. Becker
2015-06-03 21:29           ` Junio C Hamano
2015-06-04  9:01             ` John Szakmeister

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq4mmoy84y.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=eda@waniasset.com \
    --cc=git@vger.kernel.org \
    --cc=rsbecker@nexbridge.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.