http://hg.python.org/devguide/rev/9348430a4740 changeset: 448:9348430a4740 user: Éric Araujo <merwok@netwok.org> date: Wed Aug 31 16:18:19 2011 +0200 summary: Tell how to run patchcheck on Windows files: committing.rst | 3 ++- patch.rst | 9 ++++++--- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/committing.rst b/committing.rst --- a/committing.rst +++ b/committing.rst @@ -6,7 +6,8 @@ Patch Checklist --------------- -Here's the simple patch checklist that ``make patchcheck`` will run through +Here's the simple patch checklist that ``make patchcheck`` (or ``./python.exe +Tools/scripts/patchcheck.py`` on Windows) will run through on a system that uses the makefile to build Python: * Are there any whitespace problems in Python files? diff --git a/patch.rst b/patch.rst --- a/patch.rst +++ b/patch.rst @@ -118,9 +118,12 @@ This will check and/or fix various common things people forget to do for patches, such as adding any new files needed for the patch to work (note -that not all checks apply to non-core developers). +that not all checks apply to non-core developers). On Windows, use this +command:: -Assume you are using the :ref:`mq approach <mq-workflow>` suggested earlier, + ./python.exe Tools/scripts/patchcheck.py + +Assuming you are using the :ref:`mq approach <mq-workflow>` suggested earlier, first check that all your local changes have been recorded (using ``hg qrefresh``), then type the following:: @@ -131,7 +134,7 @@ help revisions``. Just please make sure that you generate a **single, condensed** patch rather than a series of several changesets. -Also, please make sure your patch is whitespace normalized. ``make patchcheck`` +Also, please make sure your patch is whitespace normalized. ``patchcheck`` will check this for you. -- Repository URL: http://hg.python.org/devguide