From: "H. Peter Anvin" <hpa@zytor•com>
To: Matthias Urlichs <smurf@smurf•noris.de>
Cc: David Mansfield <david@cobite•com>,
Jan-Benedict Glaw <jbglaw@lug-owl•de>,
Junio C Hamano <junkio@cox•net>,
Brian Gerst <bgerst@didntduck•org>,
git@vger•kernel.org
Subject: Re: [PATCH Cogito] match pathnames in exclude handling
Date: Wed, 11 May 2005 14:30:34 -0700 [thread overview]
Message-ID: <4282797A.5020001@zytor.com> (raw)
In-Reply-To: <20050511052546.GC11192@kiste.smurf.noris.de>
Matthias Urlichs wrote:
>
> I already did, last week. (I do need to cleanup my changes...)
>
> The idea is that "foo" matches anywhere, "foo/bar" the exact pathname.
> As a special case, "./foo" matches in the root directory only.
>
> NB: "*" can cross subdirectory paths, so "*/foo/bar" does match
> "a/b/c/foo/bar".
>
How does that mean foo*.c would match foo/bar/quux.c? That's probably a
bad thing.
I do like the (sadly, rarely used) convention that ** matches / whereas
* doesn't.
-hpa
next prev parent reply other threads:[~2005-05-11 21:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 23:39 [PATCH Cogito] cg-init breaks if . contains sub-dir Brandon Philips
2005-05-10 1:36 ` Morten Welinder
2005-05-10 3:41 ` Matthias Urlichs
2005-05-10 5:17 ` Brian Gerst
2005-05-10 7:52 ` Jan-Benedict Glaw
2005-05-10 8:04 ` Jan-Benedict Glaw
2005-05-10 8:36 ` Matthias Urlichs
2005-05-10 8:56 ` Martin Waitz
2005-05-10 8:56 ` Jan-Benedict Glaw
2005-05-10 9:47 ` David Greaves
2005-05-10 8:42 ` David Greaves
2005-05-10 9:01 ` Junio C Hamano
2005-05-10 9:32 ` Jan-Benedict Glaw
2005-05-10 9:39 ` Matthias Urlichs
2005-05-10 9:45 ` Jan-Benedict Glaw
2005-05-10 9:58 ` Matthias Urlichs
2005-05-10 21:31 ` David Mansfield
2005-05-11 5:25 ` [PATCH Cogito] match pathnames in exclude handling Matthias Urlichs
2005-05-11 21:30 ` H. Peter Anvin [this message]
2005-05-12 7:54 ` Matthias Urlichs
2005-05-10 15:14 ` [PATCH Cogito] cg-init breaks if . contains sub-dir H. Peter Anvin
2005-05-12 18:53 ` Petr Baudis
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=4282797A.5020001@zytor.com \
--to=hpa@zytor$(echo .)com \
--cc=bgerst@didntduck$(echo .)org \
--cc=david@cobite$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jbglaw@lug-owl$(echo .)de \
--cc=junkio@cox$(echo .)net \
--cc=smurf@smurf$(echo .)noris.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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