← Back to context Comment by firesteelrain 19 hours ago Does that cause all the binaries in LFS to come over too? 2 comments firesteelrain Reply bobmcnamara 18 hours ago 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. firesteelrain 17 hours ago 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
bobmcnamara 18 hours ago 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. firesteelrain 17 hours ago 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
firesteelrain 17 hours ago 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
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.
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