From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23618 invoked by alias); 14 Apr 2009 15:56:15 -0000 Received: (qmail 23609 invoked by uid 22791); 14 Apr 2009 15:56:14 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,HK_OBFDOM X-Spam-Check-By: sourceware.org Received: from mailhost.u-strasbg.fr (HELO mailhost.u-strasbg.fr) (130.79.200.151) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 14 Apr 2009 15:56:09 +0000 Received: from baal.u-strasbg.fr (baal.u-strasbg.fr [IPv6:2001:660:2402::41]) by mailhost.u-strasbg.fr (8.14.2/jtpda-5.5pre1) with ESMTP id n3EFtjWv090839 ; Tue, 14 Apr 2009 17:55:46 +0200 (CEST) Received: from mailserver.u-strasbg.fr (ms3.u-strasbg.fr [IPv6:2001:660:2402:d::12]) by baal.u-strasbg.fr (8.14.0/jtpda-5.5pre1) with ESMTP id n3EFti9F010569 ; Tue, 14 Apr 2009 17:55:44 +0200 (CEST) (envelope-from muller@ics.u-strasbg.fr) Received: from d620muller (www-ics.u-strasbg.fr [130.79.210.225]) (user=mullerp mech=LOGIN) by mailserver.u-strasbg.fr (8.14.3/jtpda-5.5pre1) with ESMTP id n3EFtibn044450 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) ; Tue, 14 Apr 2009 17:55:44 +0200 (CEST) (envelope-from muller@ics.u-strasbg.fr) From: "Pierre Muller" To: "'Eli Zaretskii'" Cc: Subject: [RFA] Update server name from sources.redhat.com to sourceware.org Date: Tue, 14 Apr 2009 15:56:00 -0000 Message-ID: <006701c9bd19$7b25d9c0$71718d40$@u-strasbg.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00259.txt.bz2 I the same spirit as the preceding email. This patches replaces allsources.redhat.com by sourceware.org. I don't think that there are reasons to keep the old server name in gdbint.texinfo. Pierre Muller Pascal language support maintainer for GDB gdb/doc/ChangeLog entry 2009-04-14 Pierre Muller * gdbint.texinfo: Change server name from sources.redhat.com to sourceware.org throughout. Index: gdbint.texinfo =================================================================== RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v retrieving revision 1.299 diff -u -r1.299 gdbint.texinfo --- gdbint.texinfo 21 Mar 2009 10:24:35 -0000 1.299 +++ gdbint.texinfo 14 Apr 2009 15:53:27 -0000 @@ -6709,7 +6709,7 @@ @item all commits are posted All changes committed to a branch shall also be posted to -@email{gdb-patches@@sources.redhat.com, the @value{GDBN} patches +@email{gdb-patches@@sourceware.org, the @value{GDBN} patches mailing list}. While commentary on such changes are encouraged, people should remember that the changes only apply to a branch. @@ -6876,13 +6876,13 @@ @enumerate @item -Post the proposal on @email{gdb@@sources.redhat.com, the GDB mailing +Post the proposal on @email{gdb@@sourceware.org, the GDB mailing list} Creating a bug report to track the task's state, is also highly recommended. @item Wait a week or so. @item -Post the proposal on @email{gdb-announce@@sources.redhat.com, the GDB +Post the proposal on @email{gdb-announce@@sourceware.org, the GDB Announcement mailing list}. @item Wait a week or so. @@ -6942,7 +6942,7 @@ @subheading Check the ARI -@uref{http://sources.redhat.com/gdb/ari,,A.R.I.} is an @code{awk} script +@uref{http://sourceware.org/gdb/ari,,A.R.I.} is an @code{awk} script (Awk Regression Index ;-) that checks for a number of errors and coding conventions. The checks include things like using @code{malloc} instead of @code{xmalloc} and file naming problems. There shouldn't be any @@ -6968,15 +6968,15 @@ $ D=`date -u +%Y-%m-%d` $ echo $u $V $D 5.1 5_2 2002-03-03 -$ echo cvs -f -d :ext:sources.redhat.com:/cvs/src rtag \ +$ echo cvs -f -d :ext:sourceware.org:/cvs/src rtag \ -D $D-gmt gdb_$V-$D-branchpoint insight -cvs -f -d :ext:sources.redhat.com:/cvs/src rtag +cvs -f -d :ext:sourceware.org:/cvs/src rtag -D 2002-03-03-gmt gdb_5_2-2002-03-03-branchpoint insight $ ^echo ^^ ... -$ echo cvs -f -d :ext:sources.redhat.com:/cvs/src rtag \ +$ echo cvs -f -d :ext:sourceware.org:/cvs/src rtag \ -b -r gdb_$V-$D-branchpoint gdb_$V-branch insight -cvs -f -d :ext:sources.redhat.com:/cvs/src rtag \ +cvs -f -d :ext:sourceware.org:/cvs/src rtag \ -b -r gdb_5_2-2002-03-03-branchpoint gdb_5_2-branch insight $ ^echo ^^ ... @@ -7006,9 +7006,9 @@ $ echo $u $v$V 5.1 5_2 $ cd /tmp -$ echo cvs -f -d :ext:sources.redhat.com:/cvs/src co \ +$ echo cvs -f -d :ext:sourceware.org:/cvs/src co \ -r gdb_$V-branch src/gdb/version.in -cvs -f -d :ext:sources.redhat.com:/cvs/src co +cvs -f -d :ext:sourceware.org:/cvs/src co -r gdb_5_2-branch src/gdb/version.in $ ^echo ^^ U src/gdb/version.in @@ -7069,10 +7069,10 @@ @itemize @bullet @item -@email{gdb-announce@@sources.redhat.com, GDB Announcement mailing list} +@email{gdb-announce@@sourceware.org, GDB Announcement mailing list} @item -@email{gdb@@sources.redhat.com, GDB Discussion mailing list} and -@email{gdb-testers@@sources.redhat.com, GDB Testers mailing list} +@email{gdb@@sourceware.org, GDB Discussion mailing list} and +@email{gdb-testers@@sourceware.org, GDB Testers mailing list} @end itemize @emph{Pragmatics: The branch creation is sent to the announce list to @@ -7114,7 +7114,7 @@ @subsubheading Freeze the branch Send out an e-mail notifying everyone that the branch is frozen to -@email{gdb-patches@@sources.redhat.com}. +@email{gdb-patches@@sourceware.org}. @subsubheading Establish a few defaults. @@ -7140,7 +7140,7 @@ @item Check the @code{autoconf} version carefully. You want to be using the version taken from the @file{binutils} snapshot directory, which can be -found at @uref{ftp://sources.redhat.com/pub/binutils/}. It is very +found at @uref{ftp://sourceware.org/pub/binutils/}. It is very unlikely that a system installed version of @code{autoconf} (e.g., @file{/usr/bin/autoconf}) is correct. @end itemize @@ -7345,10 +7345,10 @@ process can restart. @item Make the release candidate available in -@uref{ftp://sources.redhat.com/pub/gdb/snapshots/branch} +@uref{ftp://sourceware.org/pub/gdb/snapshots/branch} @item -Notify the relevant mailing lists ( @email{gdb@@sources.redhat.com} and -@email{gdb-testers@@sources.redhat.com} that the candidate is available. +Notify the relevant mailing lists ( @email{gdb@@sourceware.org} and +@email{gdb-testers@@sourceware.org} that the candidate is available. @end enumerate @subsection Make a formal release available @@ -7455,7 +7455,7 @@ @itemize @bullet @item -@email{gdb-announce@@sources.redhat.com, GDB Announcement mailing list} +@email{gdb-announce@@sourceware.org, GDB Announcement mailing list} @item @email{info-gnu@@gnu.org, General GNU Announcement list} (but delay it a day or so to let things get out) @@ -7519,7 +7519,7 @@ @subsubheading Revise the release schedule -Post a revised release schedule to @email{gdb@@sources.redhat.com, GDB +Post a revised release schedule to @email{gdb@@sourceware.org, GDB Discussion List} with an updated announcement. The schedule can be generated by running: @@ -7889,7 +7889,7 @@ be for quite some time. Please send patches directly to -@email{gdb-patches@@sources.redhat.com, the @value{GDBN} maintainers}. +@email{gdb-patches@@sourceware.org, the @value{GDBN} maintainers}. @section Build Script