From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Yann Dirson <ydirson@altern.org>
Cc: Christian Jaeger <christian@jaeger.mine.nu>, git@vger.kernel.org
Subject: Re: git-rm isn't the inverse action of git-add
Date: Mon, 02 Jul 2007 22:54:17 +0200 [thread overview]
Message-ID: <vpq7ipittl2.fsf@bauges.imag.fr> (raw)
In-Reply-To: <20070702204051.GP7730@nan92-1-81-57-214-146.fbx.proxad.net> (Yann Dirson's message of "Mon\, 2 Jul 2007 22\:40\:51 +0200")
Yann Dirson <ydirson@altern.org> writes:
> That is, "git rm" will only ever remove the file without asking, when
> it is safe do so, in that you can retrieve your file from history. Or
> do you think of another way, in which more safety would be needed ?
Defaulting to --cached would be an obvious way to avoid data-loss.
_At least_, mentionning --cached in the error message in case of
staged changes would be a considerable step forward.
At the moment, the non-expert user will have difficulties to unversion
the file without deleting it. I just see it as
$ git rm foo
error: 'foo' has changes staged in the index
(hint: to hang yourself, try -f)
$ _
--
Matthieu
next prev parent reply other threads:[~2007-07-02 20:55 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 [this message]
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
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=vpq7ipittl2.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=christian@jaeger.mine.nu \
--cc=git@vger.kernel.org \
--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 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.