Update crate location for 1.70.0
Jake-Shadle opened this issue · comments
Jake Shadle commented
1.70.0 made cargo's sparse protocol the default, which has a different disk location than the github crates.io index, this means that running a cargo fetch
after cargo fetcher will redo the work for all of the crates from crates.io, though much faster now due to the sparse protocol, luckily crates source from git are located elsewhere so those aren't affected.