Éric Araujo <mer...@netwok.org> added the comment: > [...] using a simple "hg status" of the working copy will not do the right > thing
I think all of these workflows share a step where you have edits in your working directory that are not in the working dir’s parent changeset. Thus, I argue that hg status is helpful in a majority of cases. In the long term, it may be better to make patchcheck work on diffs rather than $vcs status (that will be an interesting challenge for me), or something else depending on the future dev policy. That is explicitly what I’m not doing here: I’m doing a straightforward patch to add support for Mercurial in a way that just mimics Subversion, doesn’t mandate one workflow, and doesn’t cost anything. Now it’s up to you to commit this or set resolution to “later”, I won’t argue further or complain. :) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8999> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
