From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Paul Smith <paul@mad-scientist.net>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: "git rm" seems to do recursive removal even without "-r"
Date: Sat, 7 Oct 2017 17:55:48 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1710071749240.16818@localhost.localdomain> (raw)
In-Reply-To: <1507412674.8322.4.camel@mad-scientist.net>
[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]
On Sat, 7 Oct 2017, Paul Smith wrote:
> On Sat, 2017-10-07 at 15:43 -0400, Robert P. J. Day wrote:
> > it's been a long week, so take this in the spirit in which it is
> > intended ... i think the "git rm" command and its man page should be
> > printed out, run through a paper shredder, then set on fire. i can't
> > remember the last time i saw such a thoroughly badly-designed,
> > badly-documented and non-intuitive utility.
>
> "git rm" works the same way that the UNIX rm command has worked, for
> 40+ years now. Very simple, very well designed, and very intuitive
> (IMO).
>
> The major difference is the ability to handle globbing patterns,
> which UNIX rm doesn't do. Maybe the way this is implemented is a
> little confusing, although I just read the man page and it seemed
> pretty clear to me.
um, wrong.
> If you don't use glob patterns (or more specifically if you let the
> shell handle glob patterns, which is how I always do it) then there
> is really nothing bizarre about "git rm". Maybe you could be more
> precise in your criticism.
ok, fine, let me explain why this command is a nightmarish
monstrosity. as i now understand, if i use an escaped wildcard
pattern, "git rm" will *automatically* (with no further guidance from
me, and no warning), operate recursively. so if, in the kernel source
tree, i ran:
$ git rm \*.c
i would end up removing *all* 25,569 "*.c" files in the kernel source
repository.
however, let's say i wanted to remove, recursively, all files with a
*precise* (non-globbed) name, such as "Makefile". so i, naively, run:
$ git rm Makefile
guess what ... the lack of globbing means i remove only the single
Makefile at the top of the working directory.
if that isn't an example of ridiculous, non-intuitive behaviour, i
don't know what is.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2017-10-07 21:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 18:39 "git rm" seems to do recursive removal even without "-r" Robert P. J. Day
2017-10-07 19:04 ` Todd Zullinger
2017-10-07 19:12 ` Robert P. J. Day
2017-10-07 19:29 ` Jeff King
2017-10-07 19:32 ` Robert P. J. Day
2017-10-07 19:38 ` Jeff King
2017-10-07 19:43 ` Robert P. J. Day
2017-10-07 21:05 ` Theodore Ts'o
2017-10-07 21:40 ` Robert P. J. Day
2017-10-07 21:44 ` Paul Smith
2017-10-07 21:55 ` Robert P. J. Day [this message]
2017-10-08 4:20 ` Junio C Hamano
2017-10-08 9:07 ` Robert P. J. Day
2017-10-08 11:37 ` Kevin Daudt
2017-10-08 11:56 ` Robert P. J. Day
2017-10-08 12:23 ` Martin Ågren
2017-10-08 12:39 ` René Scharfe
2017-10-08 12:45 ` Robert P. J. Day
2017-10-10 11:52 ` Heiko Voigt
2017-10-11 8:31 ` Robert P. J. Day
2017-10-08 14:32 ` Paul Smith
2017-10-08 18:40 ` Theodore Ts'o
2017-10-08 19:44 ` Robert P. J. Day
2017-10-08 20:42 ` Theodore Ts'o
2017-10-09 17:52 ` Jeff King
2017-10-10 8:36 ` Robert P. J. Day
2017-10-10 8:58 ` Junio C Hamano
2017-10-10 12:19 ` Paul Smith
2017-10-10 19:44 ` Robert P. J. Day
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=alpine.LFD.2.21.1710071749240.16818@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
--cc=paul@mad-scientist.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.
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).