From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14290 invoked by alias); 11 Feb 2006 19:07:51 -0000 Received: (qmail 14281 invoked by uid 22791); 11 Feb 2006 19:07:50 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Sat, 11 Feb 2006 19:07:46 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1F805w-0006s8-4c for gdb@sourceware.org; Sat, 11 Feb 2006 14:07:44 -0500 Date: Sat, 11 Feb 2006 19:07:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Subject: Re: Copyright notices Message-ID: <20060211190743.GA26374@nevyn.them.org> Mail-Followup-To: gdb@sourceware.org References: <20060211143620.GA20537@nevyn.them.org> <20060211182727.GA25041@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00109.txt.bz2 On Sat, Feb 11, 2006 at 09:05:00PM +0200, Eli Zaretskii wrote: > > Date: Sat, 11 Feb 2006 13:27:27 -0500 > > From: Daniel Jacobowitz > > > > Well, I did not find a good non-Emacs tool for doing this; I'd rather > > using something that already exists, than write our own. It should > > just be a matter of finding all the files we consider "owned" by GDB > > (all in the gdb directory, or sim, or include/gdb/ ?) and excluding > > the generated ones. > > The above specification of which files to include/exclude sounds very > vague. Is there some existing script or algorithm that would allow to > find the relevant files programmatically? If not, then perhaps the > first good approximation would be a Dired-style command: mark the > files you want to update (or mark all of them, then unmark the ones > you don't want), and invoke a command that will update all the marked > files. WDYT? Well, what I'd do would be shell-script the above: have a script print out a list of files, and remove certain others, based on a manually defined list. (That could just be one big invocation of GNU "find"). I think the exceptions are going to be pretty small: generated documentation (e.g. man pages, info files), gdbarch.c / gdbarch.h, configure scripts, et cetera. Of course, there will still be a list of places that need to be updated by hand (including gdbarch.sh and the texinfo manuals, probably). -- Daniel Jacobowitz CodeSourcery