From: "René Scharfe" <l.s.r@web.de>
To: Git Mailing list <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>, Paul Smith <paul@mad-scientist.net>
Subject: Re: "git rm" seems to do recursive removal even without "-r"
Date: Sun, 8 Oct 2017 14:39:05 +0200 [thread overview]
Message-ID: <05775b3d-2e88-9ceb-e8d2-8ff2373cfdb5@web.de> (raw)
In-Reply-To: <alpine.LFD.2.21.1710080736530.21897@localhost.localdomain>
[My SMTP server still refuses to accept emails to rpjday@crashcourse.ca
and reports "mailbox unavailable" and "invalid DNS MX or A/AAAA resource
record." So just replying to the list.]
Am 08.10.2017 um 13:56 schrieb Robert P. J. Day:
> but as i asked in my earlier post, if i wanted to remove *all* files
> with names of "Makefile*", why can't i use:
>
> $ git rm 'Makefile*'
>
> just as i used:
>
> $ git rm '*.c'
>
> are those not both acceptable fileglobs? why does the former clearly
> only match the top-level Makefile, and refuse to cross directory
> boundaries?
>
> $ git rm -n 'Makefile*'
> rm 'Makefile'
> $
Try:
$ git rm -n '*Makefile'
The whole path is considered. The asterisk there matches any
directory part -- but also any file name prefix. Check the entry for
"pathspec" in gitglossary(7) for more details.
René
next prev parent reply other threads:[~2017-10-08 12:39 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 [this message]
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
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=05775b3d-2e88-9ceb-e8d2-8ff2373cfdb5@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).