From: Junio C Hamano <gitster@pobox•com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail•com>
Cc: git@vger•kernel.org, David Turner <dturner@twopensource•com>
Subject: Re: [PATCH v4 0/3] dt/untracked-subdir
Date: Wed, 19 Aug 2015 10:47:54 -0700 [thread overview]
Message-ID: <xmqq37zfb25x.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1439989286-24355-1-git-send-email-pclouds@gmail.com> ("Nguyễn Thái Ngọc Duy"'s message of "Wed, 19 Aug 2015 20:01:23 +0700")
Nguyễn Thái Ngọc Duy <pclouds@gmail•com> writes:
> The first patch is a split from David's v3 patch because it should
> belong to dt/untracked-sparse. The second is basically David's v3.
> The third patch fixes untracked_cache_invalidate_path(). David fixed
> it in v2, but there's another bug in this code.
>
> David Turner (1):
> untracked-cache: fix subdirectory handling
>
> Nguyễn Thái Ngọc Duy (2):
> t7063: use --force-untracked-cache to speed up a bit
> untracked cache: fix entry invalidation
>
> dir.c | 82 +++++++++++++++++++++++-------
> t/t7063-status-untracked-cache.sh | 102 ++++++++++++++++++++++++++++++++++++--
> 2 files changed, 163 insertions(+), 21 deletions(-)
They all look reasonable. Will replace v3 with these and wait a bit
to give chance to David and others to comment.
Thanks.
prev parent reply other threads:[~2015-08-19 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 5:17 [PATCH v3] untracked-cache: fix subdirectory handling David Turner
2015-08-16 12:16 ` Duy Nguyen
2015-08-19 11:39 ` Duy Nguyen
2015-08-19 13:01 ` [PATCH v4 0/3] dt/untracked-subdir Nguyễn Thái Ngọc Duy
2015-08-19 13:01 ` [PATCH v4 1/3] t7063: use --force-untracked-cache to speed up a bit Nguyễn Thái Ngọc Duy
2015-08-19 13:01 ` [PATCH v4 2/3] untracked-cache: fix subdirectory handling Nguyễn Thái Ngọc Duy
2015-08-19 13:01 ` [PATCH v4 3/3] untracked cache: fix entry invalidation Nguyễn Thái Ngọc Duy
2015-08-25 19:25 ` David Turner
2015-08-25 20:12 ` Junio C Hamano
2015-08-19 17:47 ` Junio C Hamano [this message]
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=xmqq37zfb25x.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=dturner@twopensource$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=pclouds@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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