From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12352 invoked by alias); 29 Apr 2014 21:29:24 -0000 Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org Received: (qmail 12332 invoked by uid 89); 29 Apr 2014 21:29:23 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 29 Apr 2014 21:29:22 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s3TLTH46032431 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 29 Apr 2014 17:29:17 -0400 Received: from [10.3.113.56] (ovpn-113-56.phx2.redhat.com [10.3.113.56]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id s3TLTGOG017163; Tue, 29 Apr 2014 17:29:16 -0400 Message-ID: <536019AC.1000602@redhat.com> Date: Tue, 29 Apr 2014 21:29:00 -0000 From: "Carlos O'Donell" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: "Joseph S. Myers" CC: GNU C Library , "libc-ports@sourceware.org" Subject: Re: The hppa port is now moved out of ports. References: <535F60AC.4050702@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-04/txt/msg00010.txt.bz2 On 04/29/2014 11:20 AM, Joseph S. Myers wrote: > On Tue, 29 Apr 2014, Carlos O'Donell wrote: > >> Joseph, >> >> The hppa port is now in libc. >> >> The disassembly of the shared libraries appears identical. > > Good ... since I was a bit concerned about any possible effects from the > removal of trailing whitespace in the long-double-fcts setting (see > and > ). The disassembly is identical given some local patches I still have and still get applied to gentoo and debian. In practice it only matters that long-double-fcts is equal to exactly "yes", but "no" or "no " is never used anywhere to make lists of functions or ojbects or anything of that nature. >> Is there any other next step (other than fixing >> up more of the hppa port)? > > Well, removing ports/README, leaving the directory containing just > ChangeLog files. But, yes, fixing all the hppa issues from > (all of which except the > bits needing checking against the ABIs of old binaries should be very > quick to fix). Done. I've removed README, and updated all ChangeLog.* for machines which were moved to libc proper with the normal header you were using. I've carried out the final update to ports/ChangeLog to indicate README is removed and ports is no longer in use. Please feel free to add stronger wording or another README that says "Not in use." I think we're done with the source tree. I have updated the website to say: * New port discussions should be on libc-alpha. * Use libc-ports to highlight cross-port issues so maintainers need not pay close attention to libc-alpha. * After the 2.19 release the ports add-on was merged back into core project and is no longer used. Cheers, Carlos.