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 20:31:00 -0000	[thread overview]
Message-ID: <20060211203054.GA27674@nevyn.them.org> (raw)
In-Reply-To: <20060211192051.GA4207@brasko.net> <u3bipyaac.fsf@gnu.org>

On Sat, Feb 11, 2006 at 09:18:03PM +0200, Eli Zaretskii wrote:
> > Date: Sat, 11 Feb 2006 14:07:44 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > 
> > 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.
> 
> If the exclude list is manually defined, Emacs could use it directly.

OK.  I don't know the first thing about Emacs scripting :-)  So I think
I'll defer to you on this...

> > (That could just be one big invocation of GNU "find").
> 
> Emacs already has a command to run `find' and present the results in a
> Dired-style buffer.

Gotcha.

> > 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).
> 
> What is special about Texinfo files?  The fact that Copyright appears
> there in several different places? or did you mean something else?

Right; I just figured that the in-text copyrights would have to be
updated by hand even if we auto-updated the one at the top of the
file.  Maybe that's not right.

On Sat, Feb 11, 2006 at 02:20:51PM -0500, Bob Rossi wrote:
> Of course, instead, you could use grep to look for files that 'find'
> produced and search for "Copyright (C)" to know what files should be
> updated. That way, you don't have to store a list of files that needs to
> be maintained.

No, you want to have an exclusion list rather than inclusion - you
don't want to manually futz with the copyright header in an
autoconf-generated script, for instance.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-02-11 20:31 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
2006-02-11 19:18           ` Eli Zaretskii
2006-02-11 20:31             ` Daniel Jacobowitz [this message]
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=20060211203054.GA27674@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