From: Kevin Buettner <kevinb@cygnus.com>
To: GDB Discussion <gdb@sources.redhat.com>
Subject: Re: (C) 1998-2005 for 5.1
Date: Wed, 28 Feb 2001 14:00:00 -0000 [thread overview]
Message-ID: <1010228220016.ZM18024@ocotillo.lan> (raw)
In-Reply-To: <1010228082636.ZM16394@ocotillo.lan>
There has been some discussion of the copyright update/correction
script on the gdb-patches list. One of the criticisms (and a fair one,
I think) regarding the script was made by Eli Zaretskii. Eli said:
... Adjusting the copyright notice is the responsibility of the
file's maintainers, so it isn't right IMHO for a script to
interfere like that with files I'm working on while I work on
them. The script's use should IMHO be limited to fixing past
blunders, or files for which we don't have active maintainers.
...
Eli's entire message may be read at
http://sources.redhat.com/ml/gdb-patches/2001-02/msg00502.html
I don't want the script to interfere with a maintainer's work or
responsibilities. OTOH, updating the copyright notices by hand is a
lot of work and I think that many maintainers won't mind having a bit
of help in getting them straightened out.
So... if you're a GDB maintainer and you don't want (some or all of)
the files for which you're responsible to be touched by my script,
please let me know which ones they are. So far, I have the following
files on the exclude list:
go32-nat.c
ser-go32.c
config/djgpp/README
config/djgpp/config.sed
config/djgpp/djcheck.sh
config/djgpp/djconfig.sh
config/djgpp/fnchange.lst
config/i386/go32.mh
config/i386/go32.mt
config/i386/nm-go32.h
config/i386/tm-go32.h
config/i386/xm-go32.h
Thanks,
Kevin
prev parent reply other threads:[~2001-02-28 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 9:55 Andrew Cagney
2001-02-28 0:27 ` Kevin Buettner
2001-02-28 14:00 ` Kevin Buettner [this message]
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=1010228220016.ZM18024@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=gdb@sources.redhat.com \
/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