Showing content from http://mail.python.org/pipermail/python-dev/attachments/20110105/db80efb9/attachment.html below:
<div dir="ltr"><div class="gmail_quote">On Wed, Jan 5, 2011 at 04:13, Nick Coghlan <span dir="ltr"><<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On Wed, Jan 5, 2011 at 5:55 AM, brett.cannon <<a href="mailto:python-checkins@python.org">python-checkins@python.org</a>> wrote:<br>
> brett.cannon pushed 72a286c3452d to devguide:<br>
><br>
> <a href="http://hg.python.org/devguide/rev/72a286c3452d" target="_blank">http://hg.python.org/devguide/rev/72a286c3452d</a><br>
> changeset: 13:72a286c3452d<br>
> user: Brett Cannon <<a href="mailto:brett@python.org">brett@python.org</a>><br>
> date: Tue Jan 04 11:48:38 2011 -0800<br>
> summary:<br>
> Strip out all generic svn instructions from the FAQ. It's not only<br>
> silly to duplicate instructions that can be found all over the<br>
> internet that are maintained by the creators of the tools under<br>
> discussion, but it's a maintenance burden that is unneeded.<br>
<br>
Your call as the author, but please reconsider this one. I've found it<br>
*hugely* convenient over the years to have these task oriented answers<br>
in the FAQ. The problem with the answers all over the internet is that<br>
I (or someone new to our source control tool) may not know enough to<br>
ask the right question, and hence those answers may as well not exist.<br>
Even if these FAQ answers don't always provide everything needed, they<br>
usually provide enough information to let me search for the full<br>
answers.<br>
<br></blockquote><div><br>I agree with Nick here. I also found these instructions useful in the past, although I'm quite familiar with SVN. New devs interested in contributing to Python but not too familiar with the source-control tool it's using at the time will benefit even more from this.<br>
<br>As for maintenance nightmare, I'm sure it's simple enough to attract contributors. For example, I can volunteer to maintain it.<br><br>Eli<br><br> </div></div><br></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4