On Sun, Sep 9, 2012 at 3:19 AM, georg.brandl email@example.com:
files: coredev.rst | 4 ++-- faq.rst | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/coredev.rst b/coredev.rst --- a/coredev.rst +++ b/coredev.rst @@ -25,7 +25,7 @@ able to commit them without supervision.
A complete list of core developer usernames can be found at -http://www.python.org/dev/committers. :ref:`developers` lists when and why +http://hg.python.org/committers.txt. :ref:`developers` lists when and why someone received commit privileges.
@@ -68,7 +68,7 @@ This should match your username on the issue tracker.
You can verify your commit access by looking at -http://www.python.org/dev/committers which lists all core developers by +http://hg.python.org/committers.txt which lists all core developers by username. If you want to practice, there is a `test repository http://hg.python.org/test/`_ where you can freely commit and push any changes you like:: diff --git a/faq.rst b/faq.rst --- a/faq.rst +++ b/faq.rst @@ -96,7 +96,7 @@ On the `issue tracker`_, most core developers will have the Python logo appear next to their name.
What standards of behaviour are expected in these communication channels?
-- Repository URL: http://hg.python.org/devguide
Python-checkins mailing list Pythonfirstname.lastname@example.org http://mail.python.org/mailman/listinfo/python-checkins