From: Sean MacLennan <seanm@seanm.ca>
To: git@vger.kernel.org
Subject: Request: a way to ignore .gitattributes
Date: Sat, 12 Mar 2022 13:07:12 -0500 [thread overview]
Message-ID: <20220312130712.6d9d2d00@zonker.seanm.ca> (raw)
Hi,
We have a git repo that is a mirror of an svn repo. The tools create a
huge .gitattribute file that is about 83,000 entries. Almost all are of
the form: <path> -text
This file kills git grep. A grep that takes <1s without the file takes
almost 2 minutes with the file. So git grep it unusable.
My current solution is to rename the file:
-#define GITATTRIBUTES_FILE ".gitattributes"
+#define GITATTRIBUTES_FILE ".gitattributes-no"
But I would like a cleaner solution so I don't have to maintain my own
git.
My request is more for what would be the best gitish way to solve this;
I am willing to do the actual patch.
This needs to be something in the local config and not global. My
current thoughts are:
1) A way to override the default name (much like I do now):
gitattributesfile = .gitattributes-no
2) A flag variable:
gitattributes = ignore
or
ignoreattributes = true
I personally like 1) because it would also work for the case where you
want to override a bad .gitattributes file (that you have no control
over) with a good .gitattributes file. I just think it would be more
generally useful.
But I would like to pick a solution that is most likely to get
accepted.
Cheers,
Sean MacLennan
next reply other threads:[~2022-03-12 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 18:07 Sean MacLennan [this message]
2022-03-12 21:13 ` Request: a way to ignore .gitattributes rsbecker
2022-03-12 23:50 ` Junio C Hamano
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=20220312130712.6d9d2d00@zonker.seanm.ca \
--to=seanm@seanm.ca \
--cc=git@vger.kernel.org \
/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).