3

when I use git push to my repository on bitbucket, git stuck with:

Counting objects: 70, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (60/60), done.
Writing objects: 100% (70/70), 84.86 KiB | 0 bytes/s, done.
Total 70 (delta 5), reused 0 (delta 0)

and stays here forever... I use credentials form login/pass, ssh, reinstall git and nothing. The repository is from the company that I work for, but I can create and clone repos...

João Victor
  • 639
  • 6
  • 20
  • 1
    what does the 'git push --verbose' say? – Adam Wolski Feb 24 '17 at 18:06
  • arning: push.default is unset; its implicit value has changed in Git 2.0 from 'matching' to 'simple'. To squelch this message and maintain the traditional behavior, use: git config --global push.default matching To squelch this message and adopt the new behavior now, use: git config --global push.default simple ... – João Victor Feb 24 '17 at 18:08
  • well but use your branch and remote, in the same way as you used it with the normal git push – Adam Wolski Feb 24 '17 at 18:11
  • I don't understand, I tried "git push --set-upstream origin master" and nothing change. I can commit to github, but not for bitbucket =/ – João Victor Feb 24 '17 at 18:16

1 Answers1

1

I believe this question has already been replied here

Basically, you need to increase your default git configuration 'http.postBuffer' (command -> git config --global http.postBuffer 157286400)

Sérgio Bueno
  • 99
  • 1
  • 3