Re: gitattributes - clean filter invoked on pull?

From: Miklos Vajna <vmiklos@frugalware.org>
Date: Apr 11, 2011, 09:31 UTC
Message-ID: <20110411093114.GY5146@genesis.frugalware.org>
In-Reply-To: <20110411091919.GE28959@kytes>

On Mon, Apr 11, 2011 at 02:49:21PM +0530, Ramkumar Ramachandra <artagnon@gmail.com> wrote:

Show 12 quoted lines

> > Is this a bug? I don't exactly understand why this would be necessary.
> 
> From config.txt:
> - 'clean' is "The command which is used to convert the content of a
> worktree file to a blob upon checkin".
> - 'smudge' is "The command which is used to convert the content of a
> blob object to a worktree file upon checkout."
> 
> According to the documentation, 'smudge' is *supposed* to be invoked
> on a clone/ pull, since it involves a checkout.  I don't see how you
> can avoid running these filters on every checkin/ checkout unless you
> cache the result somewhere.

That's not a problem - the issue I pointed out is that the 'clean' one is invoked on pull/clone, and it takes time if it's applied to several files.

'smudge' is just a 'cat', I don't care about it. :)

Thanks.