Demian Brecht added the comment: > Contributors may need to update their repos before this step. It would be > good to add a note about "git pull --rebase".
Working through this flow actually exposed a blocking issue as far as this guide goes. As I understand it, because Mercurial sends hashes of all topological heads in headers, the size of the headers goes quite quickly as the number of topological heads increases. When the size of the headers exceeds what the server accepts, you run into 400 responses. Details in a blog post: http://barahilia.github.io/blog/computers/2014/10/09/hg-pull-via-http-fails-400.html One of the suggested options listed in https://bitbucket.org/site/master/issue/8263/http-400-bad-request-error-when-pulling is to use SSH rather than HTTPS, but is that even an option for non core devs? I'm investigating other options right now, but thanks for pointing out the merging Berker, it definitely pointed out a flaw in this workflow. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22992> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
