From: Junio C Hamano <gitster@pobox.com>
To: <rsbecker@nexbridge.com>
Cc: "'Sean MacLennan'" <seanm@seanm.ca>, <git@vger.kernel.org>
Subject: Re: Request: a way to ignore .gitattributes
Date: Sat, 12 Mar 2022 15:50:40 -0800 [thread overview]
Message-ID: <xmqq8rten31r.fsf@gitster.g> (raw)
In-Reply-To: <01ab01d83656$071d7cd0$15587670$@nexbridge.com> (rsbecker@nexbridge.com's message of "Sat, 12 Mar 2022 16:13:26 -0500")
<rsbecker@nexbridge.com> writes:
> 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.
> 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.
Ahh, that's cleverer than what I had initially as a knee-jerk
reaction, which was "fix the tool that emits '$path -text' for each
and every path in the repository and instead use '* -text' perhaps?".
next prev parent reply other threads:[~2022-03-12 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 18:07 Request: a way to ignore .gitattributes Sean MacLennan
2022-03-12 21:13 ` rsbecker
2022-03-12 23:50 ` Junio C Hamano [this message]
2022-03-13 16:19 ` Sean MacLennan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq8rten31r.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.com \
--cc=seanm@seanm.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).