git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Etienne Vallette d'Osia <Etienne.VallettedOsia@gmail.com>
To: git@vger.kernel.org
Cc: "H.Merijn Brand" <h.m.brand@xs4all.nl>, git@vger.kernel.org
Subject: Re: On git 1.6 (novice's opinion)
Date: Fri, 27 Mar 2009 11:57:45 +0100	[thread overview]
Message-ID: <49CCB129.1070606@gmail.com> (raw)
In-Reply-To: <49CCAF5D.21814.24B4DE63@Ulrich.Windl.rkdvmks1.ngate.uni-regensburg.de>

Ulrich Windl a écrit :
>>> 3) "git undo": If possible undo the effects of the last command.
> 
> If impossible, add confirmations for some "dangerous" (non-obvious) commands 
> before doing possibly harmful things. Maybe adding a kind of "user-level setting" 
> (novice, expert, guro) could control such confirmations.
> 
Why ?
All objects stored are immutable, and some tools keep informations 
(ORIGIN_HEAD, refs/original) to allow a undo hand-made.
Moreover the reflog (and stash if you want to use it for this use) store 
  informations during time...

So it's possible to provide a generic undo for all commands that change 
refs.

Maybe an "undo" directory in $GIT_DIR, which will a keep a copy version 
of all refs. Every commands store the current refs in this folder _before_
to change anything, and the undo restore them all.
At least, a "lastcmd" (for example) file could be added in this 
directory to allow an more clever undo.

  reply	other threads:[~2009-03-27 10:59 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27  7:21 On git 1.6 (novice's opinion) Ulrich Windl
2009-03-27  8:05 ` H.Merijn Brand
2009-03-27  9:50   ` Ulrich Windl
2009-03-27 10:57     ` Etienne Vallette d'Osia [this message]
2009-03-27 11:30       ` Etienne Vallette d'Osia
2009-03-27 12:24     ` Dmitry Potapov
2009-03-27 13:39       ` Ulrich Windl
2009-03-27 13:45         ` Matthieu Moy
2009-03-27 13:47         ` Etienne Vallette d'Osia
2009-04-01  6:50           ` Ulrich Windl
2009-04-01  7:41             ` Matthieu Moy
2009-03-28  1:30         ` Junio C Hamano
2009-03-28  1:30       ` Junio C Hamano
2009-03-28  9:53         ` Dmitry Potapov
2009-03-30  6:18     ` Russ Dill
2009-04-01  7:53       ` Ulrich Windl
2009-04-01  8:37         ` Andreas Ericsson
2009-04-01  9:47           ` Ulrich Windl
2009-04-01 10:17             ` Andreas Ericsson
2009-04-01 20:37             ` Heiko Voigt
2009-03-27 12:24 ` Dmitry Potapov
2009-03-27 13:35   ` Ulrich Windl
2009-03-27 13:44     ` Matthieu Moy
2009-04-01  6:45       ` Ulrich Windl
2009-04-01  7:42         ` Matthieu Moy
2009-03-27 12:49 ` Michael J Gruber
2009-03-27 13:48   ` Ulrich Windl
2009-03-27 14:09     ` Jakub Narebski
2009-04-01  6:59       ` Ulrich Windl
2009-04-01  7:29         ` Andreas Ericsson
2009-04-01  7:54         ` Matthieu Moy
2009-04-01  9:38           ` Ulrich Windl
2009-04-01 10:10             ` Andreas Ericsson
2009-04-02  2:17         ` Jakub Narebski
2009-03-28 10:33     ` demerphq
2009-03-28  1:30 ` Junio C Hamano
2009-04-01  7:35   ` Ulrich Windl
2009-03-29  5:41 ` Bryan Donlan
2009-03-29  9:50   ` Johannes Schindelin
2009-04-01  7:42     ` Ulrich Windl
2009-04-01  7:40   ` Ulrich Windl
2009-03-30  9:06 ` Andreas Ericsson
2009-04-01  8:15   ` Ulrich Windl
2009-04-01  8:41     ` Andreas Ericsson
2009-04-01  9:55       ` Ulrich Windl
2009-04-01 10:21         ` Andreas Ericsson
2009-04-01 11:52           ` Ulrich Windl
2009-04-01 12:40             ` Andreas Ericsson
2009-04-01  2:32 ` Kris Shannon

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=49CCB129.1070606@gmail.com \
    --to=etienne.vallettedosia@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=h.m.brand@xs4all.nl \
    /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 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 NNTP newsgroup(s).