On Wed, 29 Apr 2015, Alex Pilon wrote:
> On Wed, Apr 29, 2015 at 08:33:51AM -0400, Robert P. J. Day wrote:
> > some (hopefully) trivial questions about .gitignore, since the
> > actual documentation isn't as precise as it could be.
>
> Which? gitignore(5)?
>
> > and another thing ... why both of these lines?
> >
> > include/generated
> > arch/*/include/generated
> >
> > isn't there a wildcard pattern that would subsume both of those
> > entries?
>
> **/include/generated
which brings up even more pedantry (as you knew it would) ... from
"man 5 gitignore", we read:
"If the pattern ends with a slash, it is removed for the purpose of
the following description, but it would only find a match with a
directory. In other words, foo/ will match a directory foo and paths
underneath it, ..."
in other words, "foo" would match all objects named "foo"
recursively and, in this trivial case, would be entirely equivalent
to:
**/foo
however, it's not clear whether that equivalence would be true here:
**/foo/bar
foo/bar
are *those* equivalent? based on my reading, i don't think so -- if
you want to recursively match a multi-level pathname, you would appear
to need the leading "**/", is that correct?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================