git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Duy Nguyen <pclouds@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Vipul <finn02@disroot.org>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Support for an interactive confirmation prompt when users can possibly lose their work like some UNIX commands
Date: Wed, 28 Aug 2019 22:27:35 +0700	[thread overview]
Message-ID: <CACsJy8CnaYqKSs7oCpCVSiVeferb9KJS6Fvu791BH8nBYKt6Jg@mail.gmail.com> (raw)
In-Reply-To: <20190828150530.GD14432@sigill.intra.peff.net>

On Wed, Aug 28, 2019 at 10:05 PM Jeff King <peff@peff.net> wrote:
> > > 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.

If people are interested in the backup-log thing below, they can
reuse/refine the work or the idea from that, but I'm not going to push
it (or anything else) for merging.

> I don't know the latest state. A quick search of the archive showed this
> as the latest version:
>
>   https://public-inbox.org/git/20181209104419.12639-1-pclouds@gmail.com/
-- 
Duy

  reply	other threads:[~2019-08-28 15:28 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
2019-08-28 15:27       ` Duy Nguyen [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=CACsJy8CnaYqKSs7oCpCVSiVeferb9KJS6Fvu791BH8nBYKt6Jg@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=finn02@disroot.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).