On Wed, 09 Feb 2011 21:17:51 +0100
brett.cannon python-check...@python.org wrote:
-One should always work from a checkout of the CPython source code. While it
may
+One should always work from a working copy of the CPython source code.
+While it may
be tempting to work from the
On Wed, Feb 9, 2011 at 12:29, Antoine Pitrou solip...@pitrou.net wrote:
On Wed, 09 Feb 2011 21:17:51 +0100
brett.cannon python-check...@python.org wrote:
-One should always work from a checkout of the CPython source code. While it
may
+One should always work from a working copy of the
-To get a read-only checkout of CPython's source, you need to checkout the
source
-code. To get a read-only checkout of
+To get a read-only checkout of CPython's source, you need a working copy
the
+source code. To get a read-only checkout of
Why talk about checkout at all?
Le 09/02/2011 23:49, Brett Cannon a écrit :
On Wed, Feb 9, 2011 at 12:29, Antoine Pitrou solip...@pitrou.net wrote:
-To get a read-only checkout of CPython's source, you need to checkout the
source
-code. To get a read-only checkout of
+To get a read-only checkout of CPython's source, you
On 2/9/2011 3:29 PM, Antoine Pitrou wrote:
Why talk about checkout at all? It's an SVN/CVS/RCS term, if I'm not
mistaken (even though it may occasionally be used with hg, it's a
synonym of working copy there).
I believe it harkens back to early source code control systems where one
person
