From: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Adding missing copyright years
Date: Sat, 07 May 2005 07:29:24 +0200 [thread overview]
Message-ID: <8564xv8uyz.fsf@lola.goethe.zz> (raw)
In-Reply-To: <17020.9976.943092.382629@farnswood.snap.net.nz> (Nick Roberts's message of "Sat, 7 May 2005 14:24:56 +1200")
Nick Roberts <nickrob@snap.net.nz> writes:
> > This can't be done completely mechanically, since one has to check
> > when the last copyrightable changes (and not all changes are
> > copyrightable) have been, correct?
> >
> > That's correct, aside from one subtle point. It's not that "not all
> > changes are copyrightable" but rather that "not all changes are big
> > enough to count for copyright purposes". So the question, for each
> > year, is "were substantial changes made during that year". If yes,
> > that year should be mentioned.
> >
> > Substantial means adding up to more than 10-15 lines of total change.
>
> Trying to reduce it to a formula for files whose history that we're
> not familiar with:
>
> e.g choosing cmacexp.el at random
>
> cvs annotate cmacexp.el > files.ann
>
> grep "..-...-05" cmacexp.ann | wc
> 13 104 962
>
> 13 < 15 => don't add copyright year.
>
> What are the consequences of adding a year where no copyrightable changes
> were made? Presumably this is less serious than not adding a year where
> such changes were made.
>
> How about developing a script to update these changes automatically?
Refilling a paragraph, reindenting and similar are purely mechanical
(non-copyrightable) changes with possibly large numbers of changed
lines.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-05-07 5:29 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 22:04 Adding missing copyright years Richard Stallman
2005-05-05 1:28 ` Kenichi Handa
2005-05-05 19:46 ` Richard Stallman
2005-05-06 23:42 ` Kenichi Handa
2005-05-07 18:35 ` Richard Stallman
2005-05-07 19:15 ` Juanma Barranquero
2005-05-07 23:08 ` Nick Roberts
2005-05-08 16:12 ` Richard Stallman
2005-05-08 16:11 ` Richard Stallman
2005-05-08 21:16 ` Nick Roberts
2005-05-09 21:02 ` Richard Stallman
2005-05-25 22:02 ` Bill Wohler
2005-05-26 6:00 ` Richard Stallman
2005-05-26 17:15 ` Bill Wohler
2005-05-16 7:12 ` Kenichi Handa
2005-05-16 21:20 ` Richard Stallman
2005-05-17 0:50 ` Kenichi Handa
2005-05-05 5:23 ` David Kastrup
2005-05-05 19:46 ` Richard Stallman
2005-05-07 2:24 ` Nick Roberts
2005-05-07 5:29 ` David Kastrup [this message]
2005-05-07 6:00 ` Nick Roberts
2005-05-07 9:59 ` Eli Zaretskii
2005-05-07 10:04 ` Eli Zaretskii
2005-05-07 15:07 ` Stefan Monnier
2005-05-07 15:57 ` Luc Teirlinck
2005-05-08 9:03 ` Richard Stallman
2005-05-08 9:22 ` Andreas Schwab
2005-05-09 1:35 ` Miles Bader
2005-05-09 2:06 ` Stefan Monnier
2005-05-10 21:42 ` Alexander Pohoyda
2005-05-15 22:39 ` Richard Stallman
2005-05-16 15:19 ` Alexander Pohoyda
2005-05-17 4:37 ` Richard Stallman
2005-05-07 18:35 ` Richard Stallman
2005-05-16 20:17 ` Glenn Morris
2005-05-17 4:36 ` Richard Stallman
2005-05-17 22:01 ` Kim F. Storm
2005-05-18 8:02 ` Juanma Barranquero
2005-05-18 17:53 ` Glenn Morris
2005-05-18 18:53 ` Juanma Barranquero
2005-05-18 13:08 ` Richard Stallman
2005-05-18 19:10 ` Thien-Thi Nguyen
2005-05-18 13:15 ` Thien-Thi Nguyen
2005-05-18 13:10 ` Thien-Thi Nguyen
2005-05-18 17:24 ` Glenn Morris
2005-05-20 21:57 ` Richard Stallman
2005-05-21 8:11 ` Thien-Thi Nguyen
2005-05-22 5:22 ` Kenichi Handa
2005-05-18 22:44 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8564xv8uyz.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).