Added a link to the SF CVSweb pages where the PEP histories can be

retrieved.

pep-0001.txt

@@ -25,7 +25,7 @@ What is a PEP?
 
     Because the PEPs are maintained as plain text files under CVS
     control, their revision history is the historical record of the
-    feature proposal.
+    feature proposal[1].
     
 
 Kinds of PEPs
@@ -129,7 +129,7 @@ What belongs in a successful PEP?
 
     4. Copyright/public domain -- Each PEP must either be explicitly
        labelled in the public domain or the Open Publication
-       License[1].
+       License[2].
 
     5. Specification -- The technical specification should describe
        the syntax and semantics of any new language feature.  The
@@ -162,7 +162,7 @@ PEP Style
 
     PEPs are written in plain ASCII text, and should adhere to a
     rigid style.  There is a Python script that parses this style and
-    converts the plain text PEP to HTML for viewing on the web[2].
+    converts the plain text PEP to HTML for viewing on the web[3].
 
     Each PEP begins with an RFC822 style header section.  Required
     headers are as follows, and must appear in this order:
@@ -209,13 +209,21 @@ Copyright
 
 References and Footnotes
 
-    [1] http://www.opencontent.org/openpub/
+    [1] This historical record is available by the normal CVS commands
+    for retrieving older revisions.  For those without direct access
+    to the CVS tree, you can browse the current and past PEP revisions
+    via the SourceForge web site at
 
-    [2] The script referred to here is pep2html.py, which lives in
+    http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/python/nondist/peps/?cvsroot=python
+
+    [2] http://www.opencontent.org/openpub/
+
+    [3] The script referred to here is pep2html.py, which lives in
     the same directory in the CVS tree as the PEPs themselves.  Try
     "pep2html.py --help" for details.
 
 
+
 
 Local Variables:
 mode: indented-text