Re:The Future of Large Files in Git Is Git
by HexDecOctBin on Saturday August 16, 2025 @01:37AM
(#44920490)
Why would it stop old revisions from working? What would be the difference between cloning with filter on and delete local versions from old commits?
[ Parent
| on HN ]
Re:The Future of Large Files in Git Is Git
by viraptor on Saturday August 16, 2025 @09:20AM
(#44923165)
I thought you want to prune the destination on push. Pruning local may work for some. It would be extremely annoying for me, because I'm way more likely to dig in old commits than to push. And I really don't want the existing blobs removed without an explicit consent.
Re:The Future of Large Files in Git Is Git
by yencabulator on Sunday August 17, 2025 @01:36PM
(#44933335)
Cloning with a filter does stop old revisions from working offline. checkout/merge/backfill need to be done to undo the filtering.
At some point, what you're asking for may become a configuration option, likely tied to git gc. It's not there yet because it's all experimental and nobody is paying developers to work on the feature.