unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: Kenichi Handa <handa@m17n.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Adding missing copyright years
Date: Sun, 8 May 2005 11:08:12 +1200	[thread overview]
Message-ID: <17021.19036.615336.999065@farnswood.snap.net.nz> (raw)
In-Reply-To: <f7ccd24b0505071215d0acc69@mail.gmail.com>

 > Has been suggested to use the output of annotate as a guide; that
 > would mean that only the *remaining* code is copyrightable. Is that
 > so?
 > 
 > What I mean is, if someone made a significant change to foo.el in
 > 2003, and some other people did another significant change to foo.el
 > in 2005, so there's no remaining code in foo.el from the 2003 change,
 > should the copyright be "2003, 2005" or just "2005"? I think is the
 > later (otherwise it would be imposible to expurge files from unwanted,
 > non-GPLed material that entered by accident), but I want to be sure.

So I guess you would need to run cvs annotate for each year:

e.g

cvs annotate -D 2004-12-31 cmacexp.el > cmacexp04.ann
grep "..-...-04" cmacexp04.ann | wc

cvs annotate -D 2003-12-31 cmacexp.el > cmacexp03.ann
grep "..-...-03" cmacexp03.ann | wc

It would seem that it can't be done mechanically, so maybe the (lisp) code
could invoke vc-annotate in some way for manual inspection.

Nick

  reply	other threads:[~2005-05-07 23:08 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 [this message]
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
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=17021.19036.615336.999065@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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).