Re: [PATCHv3 1/2] Documentation: clarify fnmatch behavior in gitignore
- From
Drew Northup <drew.northup@maine.edu>
- Date
- Apr 6, 2011, 12:48 UTC
- Message-ID
- <1302094097.25009.6.camel@drew-northup.unet.maine.edu>
- In-Reply-To
- <4D9B9B15.8040600@redhat.com>
On Tue, 2011-04-05 at 16:43 -0600, Eric Blake wrote:
Show 13 quoted lines
> On 04/05/2011 04:34 PM, Junio C Hamano wrote:
> >> - Otherwise, git treats the pattern as a shell glob suitable
> >> - for consumption by fnmatch(3) with the FNM_PATHNAME flag:
> >> - wildcards in the pattern will not match a / in the pathname.
> >> - For example, "Documentation/{asterisk}.html" matches
> >> + for consumption by fnmatch(3) with the FNM_PATHNAME but not
> >> + FNM_PERIOD flags: wildcards in the pattern will match leading
> >> + . but not / in pathnames. For example,
> >
> > Does this format correctly with asciidoc?
>
> No idea - I'm not an asciidoc whiz. How would I tell (or can someone
> else offer some advice)?For my ongoing project of rearranging some of the Gitweb documentation I just went ahead and made a script based on the Documentation/Makefile and run that against my in-progress work. (In that case I'll get around to munging the local Makefile later if I decide I'm really that pleased with what I've [re-]written.) This way I can incrementally become an Asciidoc genius if I really need to and remain a mortal otherwise.
-- -Drew Northup ________________________________________________ "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59