On Sun, Jul 17 2016, Jakub Wilk wrote: > Are you sure it's about git:// vs https://?
Not anymore?! > Shallow cloning has never worked for me reliably: > > $ git clone -v --depth=10 git://anonscm.debian.org/collab-maint/trend.git > Cloning into 'trend'... > Looking up anonscm.debian.org ... done. > Connecting to anonscm.debian.org (port 9418) ... 5.153.231.21 done. > fatal: The remote end hung up unexpectedly > fatal: early EOF > fatal: index-pack failed I generally clone with --depth=1, and that's what I was trying. But yes, now it doesn't work anymore even with git://. Is this intentional on alioth? [maybe to avoid extra load due to remote repack?]
