Re: gitattributes - clean filter invoked on pull?

From: Ramkumar Ramachandra <artagnon@gmail.com>
Date: Apr 11, 2011, 09:19 UTC
Message-ID: <20110411091919.GE28959@kytes>
In-Reply-To: <20110411084229.GW5146@genesis.frugalware.org>

Hi Miklos,

Miklos Vajna writes:

Show 9 quoted lines

> Background: We at LibreOffice are trying to use the 'filter'
> gitattributes feature to clean up line wrappings in po files.
> 
> 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.

>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.

-- Ram