git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Peter <peter.mx@gmail.com>
To: git@vger.kernel.org
Subject: Fwd: git rm
Date: Tue, 5 Jul 2016 23:55:24 +0200	[thread overview]
Message-ID: <CAK8tuqhMiHqPoK4gk7onT+VXsLJE5ogcpu7dc=_8am+ifL=5yQ@mail.gmail.com> (raw)
In-Reply-To: <CAK8tuqiZjfrvHCoxkFUqoDx0+9=FUxfE93aMhUkYYZAAWm-u_w@mail.gmail.com>

Greetings to the community of this wonderful piece of software!


I am a lightweigt git user so by all means not a reference, but I was
wondering why exactly does "git rm" also delete the file (remove it
from the working tree). I see it as an unintended behaviour as git is
written in a way that it preserves the most data. Usually git commands
are very basic and the usual workflow requires more consecutive
commands, it even has its own shell. But "git rm" does everything in
one step even though there are lots of scenarios where the file should
be kept. I am aware of the "git rm --cache" command, but from my
perspective "git rm --delete" is the one that is needed...

GUI users and some CLI users (by using trash-put or similar tool) also
use trash before removing the file completely. Does "git rm" support
freedesktop.org trash specification?


Thank you for your answers in advance,
Peter

       reply	other threads:[~2016-07-05 21:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAK8tuqiZjfrvHCoxkFUqoDx0+9=FUxfE93aMhUkYYZAAWm-u_w@mail.gmail.com>
2016-07-05 21:55 ` Peter [this message]
2016-07-06 16:42   ` Fwd: git rm Andreas Schwab
2016-07-07  3:35     ` Jeff King
2016-07-10  8:38       ` Peter
2016-07-10 10:57         ` Andreas Schwab
2016-07-10 12:23           ` Peter
2016-07-10 12:45             ` Andreas Schwab

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='CAK8tuqhMiHqPoK4gk7onT+VXsLJE5ogcpu7dc=_8am+ifL=5yQ@mail.gmail.com' \
    --to=peter.mx@gmail.com \
    --cc=git@vger.kernel.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. 
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).