git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: git@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: gitignore broken in git 1.7.0.1: slash checks leading dirs
Date: Fri, 05 Mar 2010 09:55:29 +0100	[thread overview]
Message-ID: <4B90C701.3070308@gmail.com> (raw)

Hi,

having 'linux' line in .gitignore makes 'include/linux/vga_switcheroo.h'
to be ignored though the documentation says:
***
If the pattern does not contain a slash /, git treats it as a shell
glob pattern and checks for a match against the pathname without
leading directories.
***

$ touch test
$ touch include/linux/vga_asdads.h
$ git ls-files -o --exclude-from=test
include/linux/vga_asdads.h
test
$ echo linux >test
$ git ls-files -o --exclude-from=test
test

This does not happen with git 1.6.

thanks,
-- 
js

             reply	other threads:[~2010-03-05  8:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05  8:55 Jiri Slaby [this message]
2010-03-05  9:05 ` gitignore broken in git 1.7.0.1: slash checks leading dirs Johannes Sixt
2010-03-05  9:07   ` Jiri Slaby
2010-03-05  9:16     ` Johannes Sixt
2010-03-05  9:20       ` [PATCH 1/1] gitignore: do not ignore include/linux/ Jiri Slaby
2010-03-05 10:43         ` Jakub Narebski
2010-03-05 15:19           ` Jiri Slaby
2010-03-10 10:07             ` David Rientjes
2010-03-10 10:11               ` Américo Wang
2010-03-10 10:25                 ` David Rientjes
2010-03-08  2:08         ` Américo Wang
2010-03-05  9:29       ` gitignore broken in git 1.7.0.1: slash checks leading dirs Jiri Slaby
2010-03-05 17:25         ` Jonathan Nieder
2010-03-05 19:30           ` Jiri Slaby
2010-03-05 15:12   ` Jonathan Nieder
2010-03-05 15:15     ` Jonathan Nieder
2010-03-05 15:34     ` Johannes Sixt
2010-03-05 15:56       ` [PATCH] gitignore.5: Clarify matching rules Jonathan Nieder
2010-03-05 17:01   ` gitignore broken in git 1.7.0.1: slash checks leading dirs Junio C Hamano

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=4B90C701.3070308@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).