From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15143 invoked by alias); 16 May 2006 22:37:02 -0000 Received: (qmail 15007 invoked by uid 22791); 16 May 2006 22:37:00 -0000 X-Spam-Check-By: sourceware.org Received: from palrel11.hp.com (HELO palrel11.hp.com) (156.153.255.246) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 16 May 2006 22:36:27 +0000 Received: from smtp2.ptp.hp.com (hpda.cup.hp.com [15.1.28.240]) by palrel11.hp.com (Postfix) with ESMTP id B232534F5C; Tue, 16 May 2006 15:36:23 -0700 (PDT) Received: from hpsje.cup.hp.com (hpsje.cup.hp.com [16.89.92.85]) by smtp2.ptp.hp.com (Postfix) with ESMTP id 5CEC6253B9F; Tue, 16 May 2006 22:36:23 +0000 (UTC) Received: (from sje@localhost) by hpsje.cup.hp.com (8.9.3 (PHNE_24419+JAGae58098)/8.7.3 TIS Messaging 5.0) id PAA29498; Tue, 16 May 2006 15:36:22 -0700 (PDT) Date: Tue, 16 May 2006 23:23:00 -0000 From: Steve Ellcey Message-Id: <200605162236.PAA29498@hpsje.cup.hp.com> To: ian@airs.com Cc: binutils@sourceware.org, gdb@sourceware.org, gcc@gcc.gnu.org Subject: Re: intl directory: gcc vs. src In-Reply-To: Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00279.txt.bz2 > > What do people who build in a combined tree do with intl? Do they use > > the GCC version or the src tree version? Is there any consensus about > > whether or not there should be a single version of intl, and if so, > > which one should be used? > > Yes, there should be a single version of intl. I don't think anybody > cares which version is used, as long as it works. If you have taken > the time to test a unified intl, and are prepared to fix any problems, > I think your patch would be great. > > Ian OK, I can sign up for that. While looking at the changes needed for the text in the MAINTAINERS file, I saw the following entry for libiberty: | libiberty/; libiberty's part of include/ | gcc: http://gcc.gnu.org | Changes need to be done in tandem with the official GCC | sources or submitted to the master file maintainer and brought | in via a merge. Note: approved patches in gcc's libiberty | are automatically approved in this libiberty also; feel free | to merge them yourself if needed sooner than the next merge. | Otherwise, changes are automatically merged, usually within | a day. Can someone tell me about this automatic merge? I was going to submit a formal patch to change the contents of src/intl but it seems that if we have an automatic merge to copy libiberty from gcc to src, we could do the same for intl (and src/config.rhost) and then I wouldn't need to do any actual checkins for those changes. If we can do that then the only thing I would need to change by hand would be the intl text that is in the MAINTAINERS file. Who maintains this automatic merge process? Steve Ellcey sje@cup.hp.com