[PATCH] install.texi: Use sourceware.org.

[Carlos O'Donell]

In BZ # 13963 a user notices that we don't consistently use
sourceware.org. 

This patch changes the manual to use sourceware.org.

2012-04-09  Carlos O'Donell  <carlos_odonell@mentor.com>

       [BZ # 13963]
       * manual/install.texi: Use sourceware.org.

diff --git a/manual/install.texi b/manual/install.texi
index 00db2b8..222ab3d 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -447,7 +447,7 @@ It is a good idea to verify that the problem has not already been
 reported.  Bugs are documented in two places: The file @file{BUGS}
 describes a number of well known bugs and the bug tracking system has a
 WWW interface at
-@url{http://sources.redhat.com/bugzilla/}.  The WWW
+@url{http://sourceware.org/bugzilla/}.  The WWW
 interface gives you access to open and closed reports.  A closed report
 normally includes a patch or a hint on solving the problem.
===

This patch changes the website to use sourceware.org and
removes the out-of-date CONFORMANCE (which also had @redhat.com
references). You should get CONFORMANCE from the source directly.

2012-04-09  Carlos O'Donell  <carlos_odonell@mentor.com>

        * bugs.html: Use sourceware.org.
        * development.html: Likewise.
        * CONFORMANCE: Remove.

Index: bugs.html
===================================================================
RCS file: /web/libc/libc/bugs.html,v
retrieving revision 1.10
diff -u -r1.10 bugs.html
--- bugs.html   23 Jan 2012 16:41:15 -0000      1.10
+++ bugs.html   9 Apr 2012 15:11:36 -0000
@@ -62,7 +62,7 @@
 </p>
 <h2>Where to file a bug?</h2>
 <p>
-  Glibc has a <a href="http://sources.redhat.com/bugzilla/">bug database</a>.
+  Glibc has a <a href="http://sourceware.org/bugzilla/">bug database</a>.
   File bugs against the product name <q>glibc</q> and select the appropriate
   version you are reporting the problem against.
 </p>
@@ -105,8 +105,8 @@
 <h2>Step 3. File a new bug</h2>
 <p>
   If your bug does not appear to exist, you may file a new bug with
-  the <a href="http://sources.redhat.com/bugzilla/enter_bug.cgi?product=glibc">new bug form</a>.
-  Bugzilla contains a <a href="http://sources.redhat.com/bugzilla/bugwritinghelp.html">general bug writing guide</a>
+  the <a href="http://sourceware.org/bugzilla/enter_bug.cgi?product=glibc">new bug form</a>.
+  Bugzilla contains a <a href="http://sourceware.org/bugzilla/bugwritinghelp.html">general bug writing guide</a>
   explaining the interface.
 </p>
 <p>
Index: development.html
===================================================================
RCS file: /web/libc/libc/development.html,v
retrieving revision 1.2
diff -u -r1.2 development.html
--- development.html    21 Mar 2012 17:59:54 -0000      1.2
+++ development.html    9 Apr 2012 15:11:36 -0000
@@ -47,7 +47,7 @@
 <p>
   The GNU C Library manual is incomplete. It would be very helpful if you could spend
   a bit of your time on writing the missing parts. Please coordinate your work with
-  the maintainers <a href="mailto:libc-alpha@sourceware.org">libc-alpha@sources.redhat.com</a>.
+  the maintainers <a href="mailto:libc-alpha@sourceware.org">libc-alpha@sourceware.org</a>.
 <h2>Porting</h2>
 <p>
   For more information on the process of porting see
@@ -55,7 +55,7 @@
   The status of ports and their sub-maintainers is currently documented on the
   <a href="http://sourceware.org/glibc/wiki/MAINTAINERS">maintainers page</a> of the wiki.
   If you are interested in porting GNU libc to additional system types, please contact
-  the maintainers <libc-ports@sources.redhat.com> before beginning your port.
+  the maintainers <a href="mailto:libc-ports@sourceware.org">libc-ports@sourceware.org</a> before beginning your port.
 </p>
 <h1>IRC</h1>
 <p>
@@ -167,7 +167,7 @@
 </form>
 <p>
   Mail archives are also available by anon-ftp in
-  <a href="ftp://sources.redhat.com/pub/glibc/mail-archives/">mbox formatted files</a>.
+  <a href="ftp://sourceware.org/pub/glibc/mail-archives/">mbox formatted files</a>.
 </p>

 </div>
===

Cheers,
Carlos.
-- 
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026