Handling of generated files after migrated to Github (python#138)

Author: ezio-melotti

setup.rst

@@ -303,20 +303,18 @@ functionality (such as using a new system call), it is necessary to update the
 Python's ``configure`` script is generated from ``configure.ac`` using Autoconf.
 Instead of editing ``configure``, edit ``configure.ac`` and then run
 ``autoreconf`` to regenerate ``configure`` and a number of other files (such as
-``pyconfig.h``.
+``pyconfig.h``).
 
-When submitting a patch with changes made to ``configure.ac``, it is preferred
-to leave out the generated files as differences between Autoconf versions
-frequently results in many spurious changes cluttering the patch. Instead,
-remind any potential reviewers on the tracker to run ``autoreconf``.
+When submitting a patch with changes made to ``configure.ac``, you should also
+include the generated files.
 
 Note that running ``autoreconf`` is not the same as running ``autoconf``. For
 example, ``autoconf`` by itself will not regenerate ``pyconfig.h.in``.
 ``autoreconf`` runs ``autoconf`` and a number of other tools repeatedly as is
 appropriate.
 
 Python's ``configure.ac`` script typically requires a specific version of
-Autoconf.  At the moment, this reads: ``version_required(2.65)``
+Autoconf.  At the moment, this reads: ``AC_PREREQ(2.65)``.
 
 If the system copy of Autoconf does not match this version, you will need to
 install your own copy of Autoconf.