Comment by viraptor
2 days ago
It's really not clear which behaviour you want though. For example when you do lots of bisects you probably want to keep everything downloaded locally. If you're just working on new things, you may want to prune the old blobs. This information only exists in your head though.
The ideal behaviour is so have a filter on push too, meaning that files above a certain size should be deleted from non-latest history after push.
That would prevent old revisions from working... Why would that be ideal?
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?
2 replies →