From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20013 invoked by alias); 25 Mar 2004 19:59:17 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 19983 invoked from network); 25 Mar 2004 19:59:16 -0000 Received: from unknown (HELO mail-out3.apple.com) (17.254.13.22) by sources.redhat.com with SMTP; 25 Mar 2004 19:59:16 -0000 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out3.apple.com (8.12.11/8.12.11) with ESMTP id i2PJxFlr004705; Thu, 25 Mar 2004 11:59:15 -0800 (PST) Received: from relay2.apple.com (relay2.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.3.6) with ESMTP id ; Thu, 25 Mar 2004 11:59:15 -0800 Received: from [17.201.22.21] (moleja.apple.com [17.201.22.21]) by relay2.apple.com (8.12.11/8.12.11) with ESMTP id i2PJwwJR011187; Thu, 25 Mar 2004 19:58:59 GMT In-Reply-To: <4062FB6D.5060108@gnu.org> References: <406239C8.6020106@apple.com> <4062FB6D.5060108@gnu.org> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: binutils@sources.redhat.com, Stan Shebs , gdb@sources.redhat.com From: Jason Molenda Subject: Re: Retire the MPW support from toplevel and binutils Date: Thu, 25 Mar 2004 22:37:00 -0000 To: Andrew Cagney X-SW-Source: 2004-03/txt/msg00569.txt.bz2 On Mar 25, 2004, at 7:31 AM, Andrew Cagney wrote: >> I'm sure you already knew this, but you'll need to update the cvs >> modules for the repository at the same time you're doing this - these >> files are explicitly named in there: > > Er, the modules file should _not_ be updated. You can always add, but > never remove entries. In this case, these support files have been obsolete for longer than the sourceware repositories have been live. From a completely maniacal outlook we'd never want to remove files like this, but looking at it realistically, there's nothing being lost here. Yes, if someone checks out binutils 2.10 (one of the first releases after the repositories moved to sourceware, circa June 2000) by a cvs command they'll be missing the mpw support files from the top level. If the modules file is not updated, every checkout until the end of time will include cvs checkout: warning: src/mpw-build.in is not (any longer) pertinent cvs checkout: warning: src/mpw-README is not (any longer) pertinent cvs checkout: warning: src/mpw-config.in is not (any longer) pertinent cvs checkout: warning: src/mpw-configure is not (any longer) pertinent cvs checkout: warning: src/mpw-install is not (any longer) pertinent Which do you think is going to cause more questions and confusion: People checking out binutils 2.10 from CVS and being shocked that the mpw support files, which no longer do anything useful, are not present, or people checking out TOT and wondering what the heck these five missing files are and why they're not pertinent. The modules file must be updated. J