Hi, On Mon, Apr 11, 2011 at 12:42 PM, Miklos Vajna <vmiklos@xxxxxxxxxxxxxx> wrote: > > The problem is that it seems the clean filter - which is supposed to be > invoked only in case a new blob is created - is invoked even on > clone/pull, and other developers are claiming that it slows down their > workflow. > > Is this a bug? I don't exactly understand why this would be necessary. No, it is not a bug. Git may invoke the clean filter when a file is not changed to make sure that the file is not changed. It is necessary to prevent a race when a file is changed so quickly that its timestamp does not change. So, what git does is compare timestamp of your file and the index file. Because the index file is written after all files, its timestamp should be later than any file in the repository. However, if the timestamp resolution is not sufficient (i.e. timestamp is the same), git may re-read recently checkout file to make sure that there were no changes to it. During this reading, the clean filter will be invoked. So, clean filter may be invoked extra time, but smudge filter should not. Dmitry -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html