From: Ben Peart <peartben@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
David Turner <David.Turner@twosigma.com>
Cc: "'Christian Couder'" <christian.couder@gmail.com>,
"Johannes Schindelin" <johannes.schindelin@gmx.de>,
git <git@vger.kernel.org>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Ben Peart" <benpeart@microsoft.com>
Subject: Re: [PATCH 0/1] Preserve the untracked cache across checkout, reset --hard, etc
Date: Tue, 9 May 2017 08:51:11 -0400 [thread overview]
Message-ID: <1e21e5c4-3440-a82f-b6c5-1a3e00439054@gmail.com> (raw)
In-Reply-To: <xmqqy3u639n4.fsf@gitster.mtv.corp.google.com>
On 5/9/2017 1:02 AM, Junio C Hamano wrote:
> David Turner <David.Turner@twosigma.com> writes:
>
>> Can you actually keep the email address as my Twopensource one? I want to make sure that Twitter, my employer at the time, gets credit for this work (just as I want to make sure that my current employer, Two Sigma, gets credit for my current work).
>>
>> Please feel free to add Signed-off-by: David Turner <dturner@twosigma.com> in case that makes tracking easier.
>>
>> Thanks.
>>
>> WRT the actual patch, I want to note that past me did not do a
>> great job here. The tests do not correctly check that the
>> post-checkout untracked cache is still valid after a checkout.
>> For example, let's say that previously, the directory foo was
>> entirely untracked (but it contained a file bar), but after the
>> checkout, there is a file foo/baz. Does the untracked cache need
>> to get updated?
>>
>> Unfortunately, the untracked cache is very unlikely to make it to
>> the top of my priority list any time soon, so I won't be able to
>> correct this test (and, if necessary, correct the code). But I
>> would strongly suggest that the test be improved before this code
>> is merged.
>>
>> Thanks for CCing me.
> I will try to find time to tweak what was sent to the list here to
> reflect your affiliations better, but marked with DONTMERGE waiting
> for the necessary updates you mentioned above, so that this change
> is not forgotten. It may turn out to be that copying from src to
> dst like the patch does is all that is needed, or the cache may need
> further invalidation when the copying happens, and I haven't got a
> good feeling that anybody who are familiar with the codepath vetted
> the correctness from seeing the discussion from sidelines (yet).
>
> Thanks.
I've been looking into similar issues with the cache associated with
using a file system monitor (aka Watchman)
(https://github.com/git-for-windows/git/compare/master...benpeart:fsmonitor)
to speed updating the index to reflect changes in the working directory.
I can take a look and see if this patch results in valid results and
reply to the thread or resubmit as needed.
Ben
next prev parent reply other threads:[~2017-05-09 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 9:41 [PATCH 0/1] Preserve the untracked cache across checkout, reset --hard, etc Johannes Schindelin
2017-05-08 9:41 ` [PATCH 1/1] unpack-trees: preserve index extensions Johannes Schindelin
2017-05-08 10:12 ` [PATCH 0/1] Preserve the untracked cache across checkout, reset --hard, etc Christian Couder
2017-05-08 15:58 ` David Turner
2017-05-09 5:02 ` Junio C Hamano
2017-05-09 12:51 ` Ben Peart [this message]
2017-05-18 16:58 ` Ben Peart
2017-05-18 17:30 ` David Turner
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=1e21e5c4-3440-a82f-b6c5-1a3e00439054@gmail.com \
--to=peartben@gmail.com \
--cc=David.Turner@twosigma.com \
--cc=benpeart@microsoft.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=pclouds@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).