Re: Should I store large text files on Git LFS?

On Tue, Jul 25, 2017 at 2:13 PM, Jeff King wrote: > On Tue, Jul 25, 2017 at 01:52:46PM -0700, Junio C Hamano wrote: > >> Jeff King writes: >> >> > As you can see, core.bigfilethreshold is a pretty blunt instrument. It >> > might be nice if .gitattributes understood

Re: Should I store large text files on Git LFS?

On Tue, Jul 25, 2017 at 01:52:46PM -0700, Junio C Hamano wrote: > Jeff King writes: > > > As you can see, core.bigfilethreshold is a pretty blunt instrument. It > > might be nice if .gitattributes understood other types of patterns > > besides filenames, so you could do something

Re: Should I store large text files on Git LFS?

Jeff King writes: > As you can see, core.bigfilethreshold is a pretty blunt instrument. It > might be nice if .gitattributes understood other types of patterns > besides filenames, so you could do something like: > > echo '[size > 500MB] delta -diff' >.gitattributes > > or

Re: Should I store large text files on Git LFS?

On Tue, Jul 25, 2017 at 06:06:49PM +1000, Andrew Ardill wrote: > Let's have a look: > > $ git rev-list --objects --all | > git cat-file --batch-check='%(objectsize:disk) %(objectsize) > %(deltabase) %(rest)' > 174 262 > 171 260

Re: Should I store large text files on Git LFS?

On 25 July 2017 at 04:11, Jeff King wrote: > On Mon, Jul 24, 2017 at 02:58:38PM +1000, Andrew Ardill wrote: > >> On 24 July 2017 at 13:45, Farshid Zavareh wrote: >> > I'll probably test this myself, but would modifying and committing a 4GB >> > text file

Re: Should I store large text files on Git LFS?

Jeff King writes: > On Mon, Jul 24, 2017 at 02:58:38PM +1000, Andrew Ardill wrote: > >> On 24 July 2017 at 13:45, Farshid Zavareh wrote: >> > I'll probably test this myself, but would modifying and committing a 4GB >> > text file actually add 4GB to the

Re: Should I store large text files on Git LFS?

On Mon, Jul 24, 2017 at 02:58:38PM +1000, Andrew Ardill wrote: > On 24 July 2017 at 13:45, Farshid Zavareh wrote: > > I'll probably test this myself, but would modifying and committing a 4GB > > text file actually add 4GB to the repository's size? I anticipate that it > >

Re: Should I store large text files on Git LFS?

Hi Farshid, On 24 July 2017 at 13:45, Farshid Zavareh wrote: > I'll probably test this myself, but would modifying and committing a 4GB > text file actually add 4GB to the repository's size? I anticipate that it > won't, since Git keeps track of the changes only, instead of

Re: Should I store large text files on Git LFS?

On Mon, 24 Jul 2017, Farshid Zavareh wrote: I'll probably test this myself, but would modifying and committing a 4GB text file actually add 4GB to the repository's size? I anticipate that it won't, since Git keeps track of the changes only, instead of storing a copy of the whole file (whereas

Re: Should I store large text files on Git LFS?

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

Re: Should I store large text files on Git LFS?

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

Re: Should I store large text files on Git LFS?

Hi Andrew. Thanks for your reply. I'll probably test this myself, but would modifying and committing a 4GB text file actually add 4GB to the repository's size? I anticipate that it won't, since Git keeps track of the changes only, instead of storing a copy of the whole file (whereas this is

Re: Should I store large text files on Git LFS?

Hi Farshid, On 24 July 2017 at 12:01, Farshid Zavareh wrote: > I'v been handed over a project that uses Git LFS for storing large CSV files. > > My understanding is that the main benefit of using Git LFS is to keep the > repository small for binary files, where Git can't

Should I store large text files on Git LFS?

Hey all. I'v been handed over a project that uses Git LFS for storing large CSV files. My understanding is that the main benefit of using Git LFS is to keep the repository small for binary files, where Git can't keep track of the changes and ends up storing whole files for each revision. For