On Apr 15 2020, Junio C Hamano wrote: > Do these (and I think we saw other reports) make us rethink the > status of protocol v2 as the default? Are all of these fallouts > we saw so far easy-to-fix bugs, or are there more fundamental issues > in the v2 protocol design? I'm now seeing the issue myself, and can provide a backup of the offending repository. $ git count-objects -v count: 17 size: 76 in-pack: 387240 packs: 37 size-pack: 203738 prune-packable: 0 garbage: 0 size-garbage: 0 alternate: /home/andreas/src/linux/git/torvalds/linux.git/objects alternate: /home/andreas/src/linux/git/stable/linux-stable.git/objects $ GIT_TRACE=1 git fetch 10:40:32.829450 git.c:439 trace: built-in: git fetch 10:40:33.133448 run-command.c:663 trace: run_command: unset GIT_DIR GIT_IMPLICIT_WORK_TREE GIT_PREFIX; git --git-dir=/daten/src/linux/git/torvalds/linux.git for-each-ref '--format=%(objectname)' 10:40:33.135756 git.c:439 trace: built-in: git for-each-ref '--format=%(objectname)' 10:40:33.143936 run-command.c:663 trace: run_command: unset GIT_DIR GIT_IMPLICIT_WORK_TREE GIT_PREFIX; git --git-dir=/daten/src/linux/git/stable/linux-stable.git for-each-ref '--format=%(objectname)' 10:40:33.146087 git.c:439 trace: built-in: git for-each-ref '--format=%(objectname)' remote: Enumerating objects: 30796, done. remote: Counting objects: 100% (30796/30796), done. remote: Compressing objects: 100% (6965/6965), done. 10:40:40.102198 run-command.c:663 trace: run_command: git index-pack --stdin -v --fix-thin '--keep=fetch-pack 12342 on igel.home' --pack_header=2,7350969 10:40:40.104872 git.c:439 trace: built-in: git index-pack --stdin -v --fix-thin '--keep=fetch-pack 12342 on igel.home' --pack_header=2,7350969 ^Cceiving objects: 0% (3092/7350969), 1.32 MiB | 891.00 KiB/s Andreas. -- Andreas Schwab, schwab@xxxxxxxxxxxxxx GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
