So my internet here is frequently
And I wanted a copy of Bar’s fork of FluidNC to have a poke at
But using GitHub Desktop failed, as did the GitHub CLI, HTTPS pull and SSH. The cause was a few too many rather large BLOBs (Binary Large OBject AKA Big Lump O’ Bytes) that would fail in some way or other mid-download and cause the ‘cloning’ of the repository to fail.
Eventually I found this in Stack Overflow Is there any way to continue Git clone from the point where it failed? - Stack Overflow
So I tweaked my command to be:
git clone --filter=blob:none --bare https://github.com/BarbourSmith/FluidNC.git
And followed that up with:
cd FluidNC.git
git rev-list --objects --all
The last command (rev-list
) will go and get all of the BLOBs that the first command deliberately left out. Most of these will actually be kinda tiny files, but the multi-megabyte files causing problems will be included. And best of all, it is recoverable after a failure.
And once everything is done - which will take ages - you can change back to the parent directory and clone from your now local bare
directory into your working directory.
cd ..
git clone FluidNC.git