On 12/07/2010 15:42, Nick Coghlan wrote:
On Mon, Jul 12, 2010 at 11:19 PM, Antoine Pitrou<solip...@pitrou.net> wrote:
+1. Don't be afraid. We are quite good at pointing out mistakes after
the fact :)
Just make sure to subscribe to python-checkins and keep an eye out for
replies to your commits. Most post hoc review comments come in as
replies to the commit notifications :)
That mailing list (python-checkins) is way too high traffic for many
committers to monitor. I hope people making comments on checkins also
email the committer directly.
All the best,
Michael
Hmm, do we mention that part of the process in the dev docs
anywhere?... and it turns out we do, as Brett included it in the Intro
to Development article.
Cheers,
Nick.
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
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.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
