Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFC] Update/correct copyright notices
Date: Wed, 28 Feb 2001 03:18:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010228130414.18772B-100000@is> (raw)
In-Reply-To: <1010228084117.ZM16412@ocotillo.lan>

On Wed, 28 Feb 2001, Kevin Buettner wrote:

> The changes below were automatically generated.  See
> 
>     http://sources.redhat.com/ml/gdb/2001-02/msg00429.html
> 
> for additional information regarding this patch.

I think the following change for go32-nat.c (and probably for many other 
files) is not right:

  diff -upr gdb.orig/go32-nat.c gdb/go32-nat.c
  --- gdb.orig/go32-nat.c Tue Feb 20 12:31:27 2001
  +++ gdb/go32-nat.c      Wed Feb 28 01:17:14 2001
  @@ -1,5 +1,5 @@
   /* Native debugging support for Intel x86 running DJGPP.
  -   Copyright 1997, 1999, 2001 Free Software Foundation, Inc.
  +   Copyright 1992, 1999, 2000, 2001 Free Software Foundation, Inc.

go32-nat.c was not part of any GDB distribution is year 2001, so I don't 
think we need, or even should, copyright it for this year yet.  What if 
the go32-nat.c changes checked into the GDB CVS until now will be 
reverted at a later date, before any release is ever made?

(I'm quite sure I saw some message from Richard Stallman which said only 
released versions need to be copyrighted, but I cannot find it in the 
references I kept.  So maybe I was dreaming.)

In any case, I suggest that Kevin's script's effect be limited to past 
years.  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.  Perhaps it should just send email to 
the responsible persons where it detects anomalies in copyright notices, 
but not actually change anything.


  parent reply	other threads:[~2001-02-28  3:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-28  0:42 Kevin Buettner
2001-02-28  0:50 ` Kevin Buettner
2001-02-28  3:20   ` Eli Zaretskii
2001-02-28  7:45     ` Andrew Cagney
2001-02-28  3:18 ` Eli Zaretskii [this message]
2001-02-28  8:52   ` Andrew Cagney
2001-02-28  9:20   ` Kevin Buettner
2001-02-28 11:11     ` Eli Zaretskii
2001-02-28 17:31 ` Andrew Cagney
2001-02-28  8:56 Michael Elizabeth Chastain
2001-02-28 14:56 ` Kevin Buettner
2001-02-28 16:24   ` Kevin Buettner
2001-03-01  0:33   ` Eli Zaretskii
2001-03-01  1:19     ` Kevin Buettner
2001-03-01  3:13       ` Eli Zaretskii
2001-02-28  9:02 Michael Elizabeth Chastain
2001-02-28  9:22 ` Kevin Buettner
2001-02-28  9:12 Michael Elizabeth Chastain
2001-02-28 15:26 Michael Elizabeth Chastain
2001-02-28 15:47 ` Stan Shebs
2001-02-28 16:36 Michael Elizabeth Chastain
2001-02-28 16:42 ` Kevin Buettner
2001-02-28 16:47 Michael Elizabeth Chastain

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=Pine.SUN.3.91.1010228130414.18772B-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@cygnus.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