On 08/11/2010 17:28, David Malcolm wrote:
On Mon, 2010-11-08 at 12:22 +0000, Michael Foord wrote:
On 08/11/2010 12:18, Łukasz Langa wrote:
On 08/11/2010 11:42, Senthil Kumaran wrote:
We can just customize our environments. It is easy. I already pointed out in my last post why that's not going to solve
Am 08.11.2010 12:55, schrieb Michael Foord: the problem.
Additional checks could be put in
make patchcheckor a local commit hook for hg. Automation always pays off. Simplifying the process always pays off. Providing yet another step to the workflow would be a move in the opposite direction*. You meanmake patchcheckisn't *already* part of your workflow? FWIW, "make patchcheck" isn't mentioned on the "Python Patch Submission Guidelines" here: http://www.python.org/dev/patches/ and doesn't seem to be mentioned anywhere on the website.I'm attaching a patch (to the website) that adds this to that page.
(snip) I've forwarded the patch to the pydotorg-www mailing list. Thanks.
All the best,
Michael Foord
--
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.