From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31637 invoked by alias); 2 Jul 2003 17:49:13 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 31625 invoked from network); 2 Jul 2003 17:49:10 -0000 Received: from unknown (HELO localhost.redhat.com) (66.187.230.200) by sources.redhat.com with SMTP; 2 Jul 2003 17:49:10 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 6BDB22B5F; Wed, 2 Jul 2003 13:49:09 -0400 (EDT) Message-ID: <3F031B15.8070803@redhat.com> Date: Wed, 02 Jul 2003 17:49:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Zack Weinberg Cc: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org Subject: Re: RFC: Moving gcc/intl to toplevel; syncing both copies to 0.12.1 References: <877k70yi2t.fsf@codesourcery.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-07/txt/msg00039.txt.bz2 Sounds like an update is long overdue. > I'd like to do this today, and commit to both gcc and src CVS > as soon as I've tested it; it is blocking another major change > over in gcc land, which needs to happen this week. Will this be > okay? Does anyone know a reason why upgrading to 0.12.1 is a bad idea? Can you two stage this - import into GCC, and then a week or so later, import in to SRC? That way the group with the most to gain (and apparently the greatest urgency) experience the most pain :-) Andrew