unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <gmorris+emacs@ast.cam.ac.uk>
Cc: emacs-devel@gnu.org
Subject: Re: Adding missing copyright years
Date: Wed, 18 May 2005 18:53:14 +0100	[thread overview]
Message-ID: <3loeb8775h.fsf@xpc14.ast.cam.ac.uk> (raw)
In-Reply-To: <f7ccd24b050518010279848f6@mail.gmail.com> (Juanma Barranquero's message of "Wed, 18 May 2005 10:02:42 +0200")


I'm trying to update the copyright in lisp/calendar, and am finding it
really tough to do a good job. FWIW, my algorithm is something like
this:

1. Make a CVS diff between 00:00 on January first of two consecutive
   years.

2. Work out the "number of lines" changed, bearing in mind that
   renaming "foo" to "bar" in lots of places counts for only one line,
   etc, etc.

3. If the number of lines changed is less than 10-15, carry the number
   forward to the next year, and add it to any changes made that year.
   If the running total becomes greater than 10-15 in any year, add a
   copyright for that year, and reset the running total to zero.

4. Modulate the above with the fact that when Emacs was not available
   via CVS, only years in which releases were made are eligible to be
   in copyright headers. So counts of changed lines should be
   accumulated until release years.

5. Keep track of code deletions. If, at any point, enough code is
   deleted so that the only remaining changes from some past year are
   no longer significant, then that year should not appear in
   copyright headers from that point onwards. This is a real PITA.


Bloomin' lawyers. Grrr...

  reply	other threads:[~2005-05-18 17:53 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
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 [this message]
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=3loeb8775h.fsf@xpc14.ast.cam.ac.uk \
    --to=gmorris+emacs@ast.cam.ac.uk \
    --cc=emacs-devel@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).