The Future of Large Files in Git Is Git

Re:The Future of Large Files in Git Is Git by firesteelrain on Friday August 15, 2025 @07:47PM (#44918571)

Yes once it gets bad enough your only option is to abandon and move the source code only. Your old repo has the history pre abandon.

[ Parent | on HN ]

Re:The Future of Large Files in Git Is Git by bobmcnamara on Saturday August 16, 2025 @10:31AM (#44923770)

There is a trick for this, where you can setup a new repo to consider another as pre-initial-commit source of history.

[ Parent | on HN ]

Re:The Future of Large Files in Git Is Git by firesteelrain on Saturday August 16, 2025 @11:51AM (#44924505)

Does that cause all the binaries in LFS to come over too?

[ Parent | on HN ]

Re:The Future of Large Files in Git Is Git by bobmcnamara on Saturday August 16, 2025 @01:19PM (#44925272)

I can't imagine it would If you were moving both git and LFS.

The old repo will still be pointed to whatever the LFS config was at that time. If that service is still up, it should continue to work.

[ Parent | on HN ]

Re:The Future of Large Files in Git Is Git by firesteelrain on Saturday August 16, 2025 @01:51PM (#44925514)

Ah my point is even with LFS enabled and you don’t store them external to git that the binaries are still totally part of the history (and really slow down cloning)

In my case, with a 25GB repo, it was really detrimental to performance

[ Parent | on HN ]