Re: What's cooking in git.git (Jun 2010, #04; Wed, 23)

From: Eyvind Bernhardsen <eyvind.bernhardsen@gmail.com>
Date: Jun 24, 2010, 20:51 UTC
Message-ID: <40D1B374-E80A-4BA2-B3A2-142E8256C23E@gmail.com>
In-Reply-To: <7veifwchb6.fsf@alter.siamese.dyndns.org>

On 24. juni 2010, at 22.21, Junio C Hamano wrote:

Show 12 quoted lines

> Finn Arne Gangstad <finnag@pvv.org> writes:
> 
>> If .gitattributes is different on the different sides, or if you
>> enable autocrlf, the current repo contents may change after
>> git-to-worktree and worktree-to-git again.
> 
> IOW, g2w-then-w2g may not be an identity function.
> 
> If we were to encourage use of this codepath to wider audiences, we may
> need to have a document for people who write smudge/clean filters.  In
> order for the result to be stable, applying g2w-then-w2g once again on top
> of the result of running g2w-then-w2g on anything should be no-op, no?

Hm.  Isn't that already a requirement?  If a clean filter doesn't clean to something normalized, simply touching a file could result in spurious differences (much like pre-safe-autocrlf autocrlf).  I could well be missing something here, though.

-- 
Eyvind