Robin Rosenberg <robin.rosenberg@xxxxxxxxxx> wrote: > Would it be hard to get the progress look better? This happens because we are scanning the progress channel wrong in some cases. Its random; most of the time we can get it right, but every once in a while we get out of sync and get these short names. This is a general problem with the progress client side code, not the new server side code I've introduced. We also see it going against a standard C git daemon. I haven't been able to figure out a way to smooth out the messages. FWIW, git-gui also gets this sort of progress corruption sometimes when it does a clone. So I've reproduced the same parsing bug in two different languages and two different implementations... ;-) > EGIT.contrib/jgit clone git://repo.or.cz/libgit2.git LIBGIT2 > Initialized empty Git repository in /home/me/SW/LIBGIT2/.git > Counting objects: 547 > Compressing objects: 100% (192/192) > ts: 100% (192/192) > Compressing objects: 100% (192/192) > ng objects: 100% (192/192) > Compressing objects: 100% (192/192) > bjects: 100% (192/192) > Compressing objects: 100% (192/192) > pressing objects: 100% (192/192) > ts: 100% (192/192) > Compressing objects: 100% (192/192) > Receiving objects: 100% (547/547) > jects: 100% (192/192) > Compressing objects: 100% (192/192) > ressing objects: 100% (192/192) > s: 100% (192/192) > Compressing objects: 100% (192/192) > ssing objects: 100% (192/192) > ts: 100% (192/192) > Compressing objects: 100% (192/192) > objects: 100% (192/192) > Compressing objects: 100% (192/192) > essing objects: 100% (192/192) > cts: 100% (192/192) > Compressing objects: 100% (192/192) > g objects: 100% (192/192) > Compressing objects: 100% (192/192) > ressing objects: 100% (192/192) > Resolving deltas: 100% (358/358) > From git://repo.or.cz/libgit2.git > * [new branch] master -> origin/master -- Shawn. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html