git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Request: a way to ignore .gitattributes

From
SMSean MacLennan <seanm@seanm.ca>
Date
Mar 13, 2022, 16:19 UTC
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:

Show 7 quoted lines
> 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
Previous: Junio C Hamano
Message 4 of 4 in “Request: a way to ignore .gitattributes”
  1. Sean MacLennanMar 12, 2022
  2. rsbecker@nexbridge.comMar 12, 2022
  3. Junio C HamanoMar 12, 2022
  4. Sean MacLennanMar 13, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.