mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <>
To: Vipul <>
Cc: "Nguyễn Thái Ngọc Duy" <>,
Subject: Re: Support for an interactive confirmation prompt when users can possibly lose their work like some UNIX commands
Date: Wed, 28 Aug 2019 11:05:30 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Aug 27, 2019 at 10:42:03PM +0000, Vipul wrote:

> Jeff King wrote:
> > The usual philosophy in Git is not to bother the user with
> > confirmations, but to allow recovery after a mistake.
> > 
> Well, always prompting for confirmation will be annoying for some people
> specially who are mastered in git but, may be very useful feature for
> beginner's to avoid them from making mistakes. May be, this feature will
> be disabled by default and users have to set some config variable (like
> other git-config variable for example help.autocorrect etc) in global
> gitconfig file.

Sure, I think there's an argument to be made for confirmations (though I
personally would not want them). I was just describing what Git has now.

> > Note that there _are_ some commands which are not reversible: mostly
> > things that drop content from the working tree. So "git reset --hard" is
> > one, and "git clean" is another. There have been discussions and even
> > some patches about storing the lost in an "undo log", but nothing has
> > been merged.
> >
> Seems like a good idea. Are they ever gonna merge? If no, why? Or, it
> will merge in next feature release.

I don't know the latest state. A quick search of the archive showed this
as the latest version:


  reply	other threads:[~2019-08-28 15:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27  9:53 Support for an interactive confirmation prompt when users can possibly lose their work like some UNIX commands Vipul
2019-08-27 19:05 ` Jeff King
2019-08-27 22:42   ` Vipul
2019-08-28 15:05     ` Jeff King [this message]
2019-08-28 15:27       ` Duy Nguyen
2019-08-27 22:22 ` Pratyush Yadav

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:

  List information:

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

  git send-email \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).