Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Copyright notices
Date: Sat, 11 Feb 2006 19:07:00 -0000	[thread overview]
Message-ID: <20060211190743.GA26374@nevyn.them.org> (raw)
In-Reply-To: <u64nlyaw3.fsf@gnu.org>

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 <drow@false.org>
> > 
> > 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


  reply	other threads:[~2006-02-11 19:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11 11:08 Eli Zaretskii
2006-02-11 11:13 ` Robert Dewar
2006-02-11 16:33   ` Eli Zaretskii
2006-02-12  3:15     ` Robert Dewar
2006-02-11 14:36 ` Daniel Jacobowitz
2006-02-11 16:30   ` Eli Zaretskii
2006-02-11 18:27     ` Daniel Jacobowitz
2006-02-11 19:05       ` Eli Zaretskii
2006-02-11 19:07         ` Daniel Jacobowitz [this message]
2006-02-11 19:18           ` Eli Zaretskii
2006-02-11 20:31             ` Daniel Jacobowitz
2006-02-11 19:19           ` Bob Rossi
2006-02-11 21:55             ` Eli Zaretskii
2006-02-12  6:09   ` Jim Blandy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060211190743.GA26374@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox