From: Anmol Sethi <me@anmol.io>
To: Jacob Keller <jacob.keller@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: Add option to git to ignore binary files unless force added
Date: Fri, 18 May 2018 14:11:10 -0400 [thread overview]
Message-ID: <B1CF9F53-D414-45E8-AA62-FE9DDD901234@anmol.io> (raw)
In-Reply-To: <CA+P7+xpdKPsWuiurD_VEF1dtV44Omfx+Mq2SN1Y1-W1vWAzX_Q@mail.gmail.com>
How about a hook to ignore certain files? Then you could ignore based on the contents of the fail instead of just the extension. It’d be very flexible.
> On May 18, 2018, at 2:09 PM, Jacob Keller <jacob.keller@gmail.com> wrote:
>
> On Fri, May 18, 2018 at 4:31 AM, Anmol Sethi <me@anmol.io> wrote:
>> This definitely works but it would be more clean to just have git ignore the binary files from the get go.
>>
>
> Sure it'd be more convenient for you. But there are loads of possible
> combinations, and the idea of what constitutes unwanted files is
> hugely variable to each user. We don't really want to end up
> supporting a million different ways to do this, and the hooks
> interface provides a reasonable method for rejecting commits with
> unwanted contents.
>
>
> Thanks,
> Jake
--
Best,
Anmol
prev parent reply other threads:[~2018-05-18 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 0:45 Add option to git to ignore binary files unless force added Anmol Sethi
2018-05-17 3:18 ` Jacob Keller
2018-05-17 12:37 ` Randall S. Becker
2018-05-18 11:31 ` Anmol Sethi
2018-05-18 15:37 ` Randall S. Becker
2018-05-18 11:31 ` Anmol Sethi
2018-05-18 18:09 ` Jacob Keller
2018-05-18 18:11 ` Anmol Sethi [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B1CF9F53-D414-45E8-AA62-FE9DDD901234@anmol.io \
--to=me@anmol.io \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).