home | list info | list archive | date index | thread index

Re: [OCLUG-Tech] more git pedantry -- clarifications about .gitignore

  • Subject: Re: [OCLUG-Tech] more git pedantry -- clarifications about .gitignore
  • From: "Robert P. J. Day" <rpjday [ at ] crashcourse [ dot ] ca>
  • Date: Wed, 29 Apr 2015 11:21:17 -0400 (EDT)
On Wed, 29 Apr 2015, Richard Guy Briggs wrote:

> On 15/04/29, Robert P. J. Day wrote:

> >   next question -- a pattern will apply to *any* file type (file or
> > directory), unless suffixed with a slash, whereupon it will apply only
> > to a directory, yes? this would appear to be the case since the kernel
> > .gitignore contains the following lines:
> >
> > /vmlinux
> > /System.map
> > ...
> > /debian/
> > /tar-install/
>
> I assume the "/" prefix anchors it in the root of the git tree...

  well, that was one of the confusing bits as i mentioned earlier ...
what does it mean if it shows up in a lower-level .gitignore. the man
page states thusly:

  A leading slash matches the beginning of the pathname. For example,
  "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c".

but if it's in a subdirectory, does it mean the pathname relative to
that subdirectory? the man page doesn't make that clear.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================