From: David Lang <david@lang.hm>
To: Farshid Zavareh <fhzavareh@gmail.com>
Cc: Andrew Ardill <andrew.ardill@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Should I store large text files on Git LFS?
Date: Sun, 23 Jul 2017 21:19:57 -0700 (PDT) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1707232119210.20418@qynat-yncgbc> (raw)
In-Reply-To: <CANENsPpdQzBqStGjq4jUsAB0-7U8_SQq+=kjmJe6pJtiXxnYFg@mail.gmail.com>
On Mon, 24 Jul 2017, Farshid Zavareh wrote:
> I see your point. So I guess it really comes down to how the file is
> anticipated to change. If only one or two line are going to change every
> now and then, then LFS is not really necessary. But, as you mentioned, text
> files that change drastically will affect the repository in the same way
> that binaries do.
Not quite the same way that binaries do, because text files compress well. but
close.
David Lang
next prev parent reply other threads:[~2017-07-24 4:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 2:01 Should I store large text files on Git LFS? Farshid Zavareh
2017-07-24 2:29 ` Andrew Ardill
2017-07-24 3:46 ` Farshid Zavareh
2017-07-24 4:13 ` David Lang
2017-07-24 4:18 ` Farshid Zavareh
[not found] ` <CANENsPpdQzBqStGjq4jUsAB0-7U8_SQq+=kjmJe6pJtiXxnYFg@mail.gmail.com>
2017-07-24 4:19 ` David Lang [this message]
[not found] ` <CANENsPr271w=a4YNOYdrp9UM4L_eA1VZMRP_UrH+NZ+2PWM_qg@mail.gmail.com>
2017-07-24 4:58 ` Andrew Ardill
2017-07-24 18:11 ` Jeff King
2017-07-24 19:41 ` Junio C Hamano
2017-07-25 8:06 ` Andrew Ardill
2017-07-25 19:13 ` Jeff King
2017-07-25 20:52 ` Junio C Hamano
2017-07-25 21:13 ` Jeff King
2017-07-25 21:38 ` Stefan Beller
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=nycvar.QRO.7.76.6.1707232119210.20418@qynat-yncgbc \
--to=david@lang.hm \
--cc=andrew.ardill@gmail.com \
--cc=fhzavareh@gmail.com \
--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.
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).