From: Dmitry Potapov <dpotapov@gmail.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: mwolfe38 <mwolfe38@gmail.com>, git@vger.kernel.org
Subject: Re: ignoring files/directories in git
Date: Mon, 22 Sep 2008 12:52:00 +0400 [thread overview]
Message-ID: <20080922085200.GI21650@dpotapov.dyndns.org> (raw)
In-Reply-To: <48D74B1C.6020408@panasas.com>
On Mon, Sep 22, 2008 at 10:37:00AM +0300, Boaz Harrosh wrote:
>
> I have 1.6.0.1 I compiled here, and it has the same problem. So it is
> a very recent fix
I certainly tested 1.6.0.1 and does not have this problem, and it was
fixed a long time ago:
===
commit d6b8fc303b389b026f2bf9918f6f83041488989b
Author: Junio C Hamano <gitster@pobox.com>
Date: Thu Jan 31 01:17:48 2008 -0800
gitignore(5): Allow "foo/" in ignore list to match directory "foo"
A pattern "foo/" in the exclude list did not match directory
"foo", but a pattern "foo" did. This attempts to extend the
exclude mechanism so that it would while not matching a regular
file or a symbolic link "foo". In order to differentiate a
directory and non directory, this passes down the type of path
being checked to excluded() function.
A downside is that the recursive directory walk may need to run
lstat(2) more often on systems whose "struct dirent" do not give
the type of the entry; earlier it did not have to do so for an
excluded path, but we now need to figure out if a path is a
directory before deciding to exclude it. This is especially bad
because an idea similar to the earlier CE_UPTODATE optimization
to reduce number of lstat(2) calls would by definition not apply
to the codepaths involved, as (1) directories will not be
registered in the index, and (2) excluded paths will not be in
the index anyway.
===
The patch is included in 1.5.5.
Dmitry
next prev parent reply other threads:[~2008-09-22 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 16:54 ignoring files/directories in git mwolfe38
2008-09-21 17:19 ` Boaz Harrosh
2008-09-21 17:20 ` Alex Riesen
2008-09-21 17:42 ` mwolfe38
2008-09-22 18:47 ` Tim Harper
2008-09-21 17:42 ` Dmitry Potapov
2008-09-22 0:06 ` mwolfe38
2008-09-22 7:37 ` Boaz Harrosh
2008-09-22 8:52 ` Dmitry Potapov [this message]
2008-09-22 10:41 ` Boaz Harrosh
2008-09-22 11:53 ` Andreas Ericsson
2008-09-22 12:19 ` Dmitry Potapov
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=20080922085200.GI21650@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=bharrosh@panasas.com \
--cc=git@vger.kernel.org \
--cc=mwolfe38@gmail.com \
/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).