From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Jeff King <peff@peff.net>
Cc: Theodore Ts'o <tytso@mit.edu>,
Paul Smith <paul@mad-scientist.net>,
Git Mailing list <git@vger.kernel.org>
Subject: Re: "git rm" seems to do recursive removal even without "-r"
Date: Tue, 10 Oct 2017 04:36:53 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1710100432220.16182@localhost.localdomain> (raw)
In-Reply-To: <20171009175225.qn6a3j2th3dxjjn2@sigill.intra.peff.net>
On Mon, 9 Oct 2017, Jeff King wrote:
> On Sun, Oct 08, 2017 at 04:42:27PM -0400, Theodore Ts'o wrote:
>
> > On Sun, Oct 08, 2017 at 03:44:14PM -0400, Robert P. J. Day wrote:
> > > >
> > > > find <find args> | xargs git rm
> > > >
> > > > myself.
> > >
> > > that's what i would have normally used until i learned about
> > > git's magical globbing capabilities, and i'm going to go back to
> > > using it, because git's magical globbing capabilities now scare
> > > me.
> >
> > Hmm, I wonder if the reason why git's magically globbing
> > capabilities even exist at all is for those poor benighted souls
> > on Windows, for which their shell (and associated utilities)
> > doesn't have advanced tools like "find" and "xargs"....
>
> One benefit of globbing with Git is that it restricts the matches
> only to tracked files. That matters a lot when you have a very broad
> glob (e.g., like you might use with "git grep") because it avoids
> looking at cruft like generated files (or even inside .git).
ah, now *that* is a compelling rationale that justifies the
underlying weirdness. but it still doesn't explain the different
behaviour between:
$ git rm -n 'Makefile*'
$ git rm -n '*Makefile'
in the linux kernel source tree, the first form matches only the
single, top-level Makefile, while the second form gets *all* of them
recursively, even though those globs should be equivalent in terms of
matching all files named "Makefile".
am i misunderstanding something?
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-10 8:37 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
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 [this message]
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
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=alpine.LFD.2.21.1710100432220.16182@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
--cc=paul@mad-scientist.net \
--cc=peff@peff.net \
--cc=tytso@mit.edu \
/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).