Re: How to simulate a real checkout to test a new smudge filter?

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 9, 2016, 23:12 UTC
Message-ID: <xmqqd1kc8y6i.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAKmQUfYCUq=kUTau1-3NjjPVBk6WkP3KdTjgMC8sZtU8h=H4iQ@mail.gmail.com>

john smith <wempwer@gmail.com> writes:

Show 6 quoted lines

> ... get it.  The problem is that in the scenario presented in my last
> e-mail clean filter is run in the situation which doesn't like a
> checkin to me.  Is `git checkout <PATH>' doing a *checkin*" under the
> hood so that the clean filter is called?  What does actually `checkin'
> mean in Git?  I thought that checkin it's the same as committing a
> file into the repository.

I do not know what Jakub meant.

When we need to see if we need to update a working tree file, and when we cannot tell if you modified the working tree file since you checked it out, we may have to run the clean filter (and other conversions collectively called "convert-to-git") on the contents in it and see if the resulting blob matches what is recorded in the index (if they match, there is no need to update the working tree file; if they don't match, we either report that you have a local modification, or we overwrite it with the contents, depending on what operation we are doing for the user).