➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients belopolsky, brett.cannon, eric.araujo, mark.dickinson, pitrou
Date 2010-06-23.14:48:21
SpamBayes Score 0.1726044
Marked as misclassified No
Message-id <1277304503.36.0.99109426913.issue8999@psf.upfronthosting.co.za>
In-reply-to
Content 
The purpose of patchcheck.py is not obvious to me. If it's meant to be used by committers (rather than contributors), than we should wait for the actual hg migration and the definition of our new workflow. Also, we might "need" two separate scripts: one for individual changesets and one for pushes.

("need" is in quotes because I'm not sure anyone actually uses patchcheck.py)
History
Date User Action Args
2010-06-23 14:48:23pitrousetrecipients: + pitrou, brett.cannon, mark.dickinson, belopolsky, eric.araujo
2010-06-23 14:48:23pitrousetmessageid: <1277304503.36.0.99109426913.issue8999@psf.upfronthosting.co.za>
2010-06-23 14:48:21pitroulinkissue8999 messages
2010-06-23 14:48:21pitroucreate