Re: [PATCH] Create a new manpage for the gitignore format, and reference it elsewhere
- From
Frank Lichtenheld <djpig@debian.org>
- Date
- Jun 2, 2007, 10:56 UTC
- Message-ID
- <20070602105648.GX3242@planck.djpig.de>
- In-Reply-To
- <4660BF65.3000605@freedesktop.org>
On Fri, Jun 01, 2007 at 05:52:53PM -0700, Josh Triplett wrote:
Show 16 quoted lines
> Frank Lichtenheld wrote: > > On Fri, Jun 01, 2007 at 03:20:52PM -0700, Josh Triplett wrote: > >> + - Otherwise, git treats the pattern as a shell glob suitable > >> + for consumption by fnmatch(3) with the FNM_PATHNAME flag: any > >> + slash in the pattern must match a slash in the pathname. For > >> + example, "Documentation/\*.html" matches > >> + "Documentation/git.html" but not "ppc/ppc.html". A leading > >> + slash matches the beginning of the pathname; for example, > >> + "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c". > > > > I realise this is copy&paste but shouldn't that read: > > "Documentation/\*.html" matches "Documentation/git.html" > > but not "Documentation/ppc/ppc.html" > > ? > > I don't know. Neither file seems to exist in current Git.
The point I was trying to make is that "Documentation/*.html" _of course_ doesn't match ppc/ppc.html. What we try to tell the user here is that * doesn't match / So I think it should definetly read Documentation/ppc/ppc.html FWIW, I find the sentence "any slash in the pattern must match a slash in the pathname" very confusing too. The sentence in fnmatch(3) is much more precise: "match a slash in string only with a slash in pattern and not by an asterisk (*) or a question mark (?) metacharacter, nor by a bracket expression ([]) containing a slash"
Anyway, if you prefer (and if it is okay with Junio) I can send a patch of my own for this single issue to not hinder the commit of your big patch as the issue is equally present in the old and the new text.
Gruesse,
-- Frank Lichtenheld <djpig@debian.org> www: http://www.djpig.de/