From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Jaeger <christian@jaeger.mine.nu>,
Yann Dirson <ydirson@altern.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: git-rm isn't the inverse action of git-add
Date: Tue, 3 Jul 2007 01:12:54 -0400 [thread overview]
Message-ID: <20070703051254.GA6477@coredump.intra.peff.net> (raw)
In-Reply-To: <7v4pkmt6nk.fsf@assigned-by-dhcp.cox.net>
On Mon, Jul 02, 2007 at 10:09:35PM -0700, Junio C Hamano wrote:
> Exactly. And not considering that lossage helps us keep our
> sanity. I think "git rm --cached" falls into the same
> category. If the user wants to discard what is in the index
> without losing a copy in the working tree, I think we should let
> him do without fuss.
OK. So should we _remove_ the safety valve in all cases where we're just
losing stuff that's in the index? It is, after all, recoverable. Should
there be a warning (I suspect it would get annoying very quickly)?
I think this would help by making the use of '-f' more rare, which is
the thing that can _really_ screw you, since it turns off the safety
valve even for things that aren't recoverable.
-Peff
next prev parent reply other threads:[~2007-07-03 5:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 18:09 git-rm isn't the inverse action of git-add Christian Jaeger
2007-07-02 19:42 ` Yann Dirson
2007-07-02 20:23 ` Christian Jaeger
2007-07-02 20:40 ` Yann Dirson
2007-07-02 20:54 ` Matthieu Moy
2007-07-02 21:05 ` Johannes Schindelin
2007-07-03 10:37 ` Matthieu Moy
2007-07-03 12:09 ` Johannes Schindelin
2007-07-03 13:40 ` Matthieu Moy
2007-07-03 14:21 ` Johannes Schindelin
2007-07-04 20:08 ` Jan Hudec
2007-07-05 13:44 ` Matthieu Moy
2007-07-05 14:00 ` David Kastrup
2007-07-08 17:36 ` [RFC][PATCH] " Matthieu Moy
2007-07-08 18:10 ` Johannes Schindelin
2007-07-08 20:34 ` Matthieu Moy
2007-07-08 21:49 ` Johannes Schindelin
2007-07-09 9:45 ` Matthieu Moy
2007-07-13 17:36 ` Matthieu Moy
2007-07-13 17:41 ` [PATCH] More permissive "git-rm --cached" behavior without -f Matthieu Moy
2007-07-13 17:57 ` Jeff King
2007-07-13 18:53 ` Matthieu Moy
2007-07-14 3:42 ` Jeff King
2007-07-14 0:44 ` Jakub Narebski
2007-07-14 6:52 ` Junio C Hamano
2007-07-14 7:16 ` Junio C Hamano
2007-07-14 10:14 ` Matthieu Moy
2007-07-02 21:20 ` git-rm isn't the inverse action of git-add Christian Jaeger
2007-07-03 4:12 ` Jeff King
2007-07-03 4:47 ` Junio C Hamano
2007-07-03 4:59 ` Jeff King
2007-07-03 5:09 ` Junio C Hamano
2007-07-03 5:12 ` Jeff King [this message]
2007-07-03 6:26 ` Junio C Hamano
2007-07-11 12:20 ` Jakub Narebski
2007-07-11 18:56 ` Jan Hudec
2007-07-11 21:26 ` Junio C Hamano
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=20070703051254.GA6477@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian@jaeger.mine.nu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ydirson@altern.org \
/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).