From c0b589e388d5698ebd4f216e6a8e69770daf1cae Mon Sep 17 00:00:00 2001 From: Barry Warsaw Date: Mon, 8 Aug 2005 04:03:40 +0000 Subject: [PATCH] Fixed some minor typos. --- pep-0347.txt | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/pep-0347.txt b/pep-0347.txt index 7e81e9bc4..8743ea0fe 100644 --- a/pep-0347.txt +++ b/pep-0347.txt @@ -15,21 +15,21 @@ Abstract ======== The Python source code is currently managed in a CVS repository on -sourceforge.net. This PEP proposes to move it to a subversion +sourceforge.net. This PEP proposes to move it to a Subversion repository on svn.python.org. Rationale ========= -This change has two aspects: moving from CVS to subversion, and moving +This change has two aspects: moving from CVS to Subversion, and moving from SourceForge to python.org. For each, a rationale will be given. Moving to Subversion -------------------- -CVS has a number of limitations that have been elimintation by +CVS has a number of limitations that have been eliminated by Subversion. For the development of Python, the most notable improvements are: @@ -41,7 +41,7 @@ improvements are: transactional. - atomic, fast tagging: a cvs tag might take many minutes; a - subversion tag (svn cp) will complete quickly, and atomically. + Subversion tag (svn cp) will complete quickly, and atomically. Likewise, branches are very efficient. - support for offline diffs, which is useful when creating patches. @@ -128,10 +128,10 @@ structure. A project will be created for each nondist directory, plus for src (called python), plus distutils. Reorganizing the repository is best done in the CVS tree, as shown below. -Fsfs should be used as the repository format (requires Subversion -1.1). Fsfs has the advantage of being more backup-friendly, as it -allows incremental repository backups, without requiring any dump -commands to be run. +The fsfs backend should be used as the repository format (which +requires Subversion 1.1). The fsfs has the advantage of being more +backup-friendly, as it allows incremental repository backups, without +requiring any dump commands to be run. The conversion should be done using the cvs2svn utility, available e.g. in the cvs2svn Debian package. As cvs2svn does not currently @@ -205,7 +205,7 @@ The rejected alternatives are shortly discussed here: across projects. - Nick Bastin has offered to host a Perforce repository, instead - of using subversion. Details of that offer are not clear yet. + of using Subversion. Details of that offer are not clear yet. - Several people suggested to create the project/trunk structure through standard cvs2svn, followed by renames. This would have @@ -230,8 +230,7 @@ The rejected alternatives are shortly discussed here: decided. * Subversion over WebDAV, using SSL client certificates. This would - work, but would require us to administrate a certificate - authority. + work, but would require us to administer a certificate authority. Copyright