Are there any commands that I can use to show exactly what it is trying to push? I'll see if I can create a (public) repo that has the same problem. Thanks for your help. > This 10804 looks wrong (i.e. sending that many compressed objects). > Also "80 MiB" sent at that point. If you modify just a couple files, > something is really wrong because the number of new objects may be > hundreds at most, not thousands. > > v2.2.2 supports "git fast-export --anonymize" [1] to create an > anonymized "clone" of your repo that you can share, which might help > us understand the problem. > > There's also the environment variable GIT_TRACE_PACKET that can help > see what's going on at the protocol level, but I think you're on your > own because without access to this repo, SHA-1s from that trace may > not make much sense. > > [1] https://github.com/git/git/commit/a8722750985a53cc502a66ae3d68a9e42c7fdb98 > -- > Duy -- 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