Demian Brecht added the comment: Thanks for the comments, will try to have an updated patch today.
> Trying to learn usual hg workflows might also be easier than trying to use a > git-like workflow on mercurial, so you could suggest considering them too (I > don't remember if we have anything about it in the devguide though). (For other as we briefly chatted about this over IM:) The intention of this guide was to minimize the cognitive load of context switching between git and mercurial projects for git developers just beginning to use mercurial. As their experience with mercurial increases, their workflow may change to be more of an "out of the box" type flow. Git developers (myself included) will likely spend a good deal of time trying to figure out "how to do X as I would in git using Mercurial". This is simply to try and lower the initial cost of development for new contributors. ---------- _______________________________________ 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
