Update ports README file.

diff --git a/ChangeLog b/ChangeLog
index 378cf26..6a37d34 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
 2012-02-07  Joseph Myers  <joseph@codesourcery.com>
 
+       * README: Update.
+
+2012-02-07  Joseph Myers  <joseph@codesourcery.com>
+
        * README: Document use of ranges in copyright notices.
 
 2011-11-29  Joseph Myers  <joseph@codesourcery.com>

diff --git a/README b/README
index 3ad8078..51e0a30 100644 (file)
--- a/README
+++ b/README
@@ -9,11 +9,12 @@ some optimized functions tailored for specific CPU implementations of an
 architecture, to be selected using --with-cpu.
 
 The ports repository is cooperatively maintained by volunteers on the
-<libc-ports@sourceware.org> mailing list, and housed in the glibc CVS as a
-module called "ports".  See http://www.gnu.org/software/libc/resources.html
-for details on using CVS.  To report a bug in code housed in the ports
-repository, please go to http://sources.redhat.com/bugzilla/ and file a bug
-report under the glibc "ports" component.
+<libc-ports@sourceware.org> mailing list, and housed in a separate
+ports git repository.  See
+http://www.gnu.org/software/libc/download.html for details on using
+git.  To report a bug in code housed in the ports repository, please
+go to http://sources.redhat.com/bugzilla/ and file a bug report under
+the glibc "ports" component.
 
 An add-on for an individual port can be made from just the sysdeps/
 subdirectories containing the port's code.  You may want to include a
@@ -34,7 +35,8 @@ sysdeps/CPU/preconfigure file; this can either be written by hand or
 generated by Autoconf from sysdeps/CPU/preconfigure.in, and follow the
 rules for glibc add-on configure fragments.  No preconfigure file should do
 anything on an unrelated configuration, so that disparate ports can be put
-into a single add-on without interfering with each other.
+into a single add-on without interfering with each other.  Files that
+would go in scripts/data/ for libc go in data/ in ports.
 
 Like all glibc add-ons, this must be used by specifying the directory in
 the --enable-add-ons option when running glibc's configure script.