git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Avery Pennarun <apenwarr@gmail.com>,
	SungHyun Nam <goweol@gmail.com>,
	git@vger.kernel.org
Subject: Re: 'git add' regression in git-1.7?
Date: Tue, 9 Mar 2010 18:09:31 -0500	[thread overview]
Message-ID: <20100309230931.GC25265@sigill.intra.peff.net> (raw)
In-Reply-To: <20100309223729.GA25265@sigill.intra.peff.net>

On Tue, Mar 09, 2010 at 05:37:30PM -0500, Jeff King wrote:

> No, we would still be correct if we recurse into the ignored directory
> _only_ to collect the ignored bits (so we don't even bother if
> COLLECT_IGNORED isn't set). But what I don't like is that you take a
> performance hit, because in most cases you won't ever care what's inside
> those directories. You need to recurse only when:
> 
>   - you actually care about all files. git-add does. git-status does not
>     (unless you explicitly told it to show directories). So that would
>     probably need a flag passed to fill_directory.
> 
>   - you have a pathspec that means the contents of the directory might
>     be interesting. Right now we check in_pathspec in treat_one_path.
>     But I think we would need to recognize that "subdir/file" is
>     means "subdir" is in our pathspec (and that "sub*" means the same
>     thing).

Actually, if we accept that the message simply mentions the excluded
path, i.e.:

  $ git add subdir/file
  The following paths are ignored by one of your .gitignore files:
  subdir
  Use -f if you really want to add them.

then we don't really need to recurse. We just need to fix in_pathspec to
flag files that are _relevant_ to a pathspec.

And something like this seems to fix the OP's problem:

diff --git a/dir.c b/dir.c
index 00d698d..5091bfd 100644
--- a/dir.c
+++ b/dir.c
@@ -554,13 +554,17 @@ static int simplify_away(const char *path, int pathlen, const struct path_simpli
 	return 0;
 }
 
-static int in_pathspec(const char *path, int len, const struct path_simplify *simplify)
+static int relevant_pathspec(const char *path, int len, const struct path_simplify *simplify)
 {
 	if (simplify) {
 		for (; simplify->path; simplify++) {
 			if (len == simplify->len
 			    && !memcmp(path, simplify->path, len))
 				return 1;
+			if (len < simplify->len
+			    && simplify->path[len] == '/'
+			    && !memcmp(path, simplify->path, len))
+				return 1;
 		}
 	}
 	return 0;
@@ -638,7 +642,7 @@ static enum path_treatment treat_one_path(struct dir_struct *dir,
 {
 	int exclude = excluded(dir, path, &dtype);
 	if (exclude && (dir->flags & DIR_COLLECT_IGNORED)
-	    && in_pathspec(path, *len, simplify))
+	    && relevant_pathspec(path, *len, simplify))
 		dir_add_ignored(dir, path, *len);
 
 	/*

Which is similar to your fix, but hoisted into the ignore-collection
phase. Like the original code and your patch, it suffers from using a
straight memcmp. I think it should actually be checking the pathspec
expansion to catch things like 'sub*/file' being relevant to 'subdir'.

-Peff

  reply	other threads:[~2010-03-09 23:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19  4:30 'git add' regression in git-1.7? SungHyun Nam
2010-02-19  4:42 ` Avery Pennarun
2010-02-19  5:04   ` SungHyun Nam
2010-02-19  5:15     ` Avery Pennarun
2010-02-19  5:34       ` Jeff King
2010-02-19  6:02         ` Jeff King
2010-02-19  8:24           ` Jeff King
2010-03-01  2:00             ` Junio C Hamano
2010-03-01  3:25               ` [PATCH] add: fail "git add ignored-dir/file" without -f Junio C Hamano
2010-03-01  8:26                 ` [PATCH 1/3] t0050: mark non-working test as such Junio C Hamano
2010-03-09 22:37               ` 'git add' regression in git-1.7? Jeff King
2010-03-09 23:09                 ` Jeff King [this message]
2010-03-10  7:06                   ` Junio C Hamano
2010-03-11  7:15                     ` Jeff King
2010-03-14  6:34                       ` Junio C Hamano
2010-03-14 20:44                         ` Jeff King
2010-03-15  2:02                           ` 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=20100309230931.GC25265@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=goweol@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).