From: Sean MacLennan <seanm@seanm.ca>
Date: Sun, 13 Mar 2022 16:19:51 GMT
Subject: Re: Request: a way to ignore .gitattributes
Message-ID: <20220313121951.093495fb@zonker.seanm.ca>
In-Reply-To: <01ab01d83656$071d7cd0$15587670$@nexbridge.com>

On Sat, 12 Mar 2022 16:13:26 -0500
<rsbecker@nexbridge.com> wrote:

> These may seem a little off the wall, but:
> 1. Could you use a clean/smudge approach to mess with your bad
> .gitattributes file before it gets put down on disk? I realize that
> registering the filter might not be possible given that you need to
> muck with .gitattributes to do it, but if you have any control at all
> and can get the filter in, perhaps that might be a way to clean up
> the bad .gitattributes file.

I have no access to the servers.

> 2. What about a post-checkout hook that fixes .gitattributes and then
> does an update-index --assume-unchanged on it. This is under the
> assumption that you will never change .gitattributes in your clone.

That seems to work. I did not know about update-index.

> My $0.02,
> --Randall

Cheers,
   Sean