All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Ed Avis <eda@waniasset.com>, git@vger.kernel.org
Subject: Re: Suggestion: make git checkout safer
Date: Wed, 03 Jun 2015 14:29:21 -0700	[thread overview]
Message-ID: <xmqqiob4wkem.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150603190616.GA28488@peff.net> (Jeff King's message of "Wed, 3 Jun 2015 15:06:16 -0400")

Jeff King <peff@peff.net> writes:

> On Wed, Jun 03, 2015 at 10:32:40AM -0700, Junio C Hamano wrote:
>
> Yeah, I'd say "cp -i" is the closest thing. I don't have a problem with
> adding that, but I'd really hate for it to be the default (just as I
> find distros which "alias rm='rm -i" annoying).

Oh, no question about it.

I think a typical user cease to be a newbie before having to type
"-i" every time starts to annoy her, and instead will learn to use
the tool more effectively and efficiently [*1*], so making "-i"
default is not good not just for you but for everybody.


[Footnote]

*1* In the context of this discussion, after screwing up the change
    in hello.c, instead of expressing the wish to recover and to
    start from scratch in two separate commands, i.e.

	rm hello.c && update-from-scm

    they will learn to use a single command that is designed for
    that purpose, i.e.

	checkout-from-scm hello.c

    without the "rm" step, which _is_ an artificial workaround for
    their other SCMs that do not update from the repository unless
    they remove the files.

  parent reply	other threads:[~2015-06-03 21:29 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
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 [this message]
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=xmqqiob4wkem.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=eda@waniasset.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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.