From: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: Piet van Oostrum <piet@cs.uu.nl>, emacs-devel@gnu.org
Subject: Re: Finish updating copyright years
Date: 31 Oct 2005 08:26:09 -0800 [thread overview]
Message-ID: <86vezdlkke.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <m3fyqhemsw.fsf@kfs-l.imdomain.dk>
>>>>> "Kim" == Kim F Storm <storm@cua.dk> writes:
Kim> But take emacs/src/xdisp.c as an example. It is 23750 lines of C code.
Kim> Now, suppose I changed 25 lines in that file. So only a fraction of
Kim> the file is new creativity, but still I would update the copyright to
Kim> say (C) 2005.
And you would be wrong, according to my sources. You should change
that file to say (c) 2004, 2005.
Kim> We can argue about this issue forever, but if our lawyer says the
Kim> policy is ok, I'm ok with that.
And that's why I'm not arguing for change, just making sure I'm clear
on everyone's point and everyone is clear on mine.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2005-10-31 16:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 1:14 Finish updating copyright years Richard M. Stallman
2005-10-31 6:19 ` Randal L. Schwartz
2005-10-31 9:56 ` David Kastrup
2005-10-31 11:47 ` Nick Roberts
2005-10-31 13:03 ` Randal L. Schwartz
2005-10-31 12:49 ` Piet van Oostrum
2005-10-31 14:05 ` Randal L. Schwartz
2005-10-31 14:22 ` Piet van Oostrum
2005-10-31 14:34 ` Randal L. Schwartz
2005-10-31 14:58 ` Kim F. Storm
2005-10-31 15:02 ` Randal L. Schwartz
2005-10-31 15:19 ` Kim F. Storm
2005-10-31 16:26 ` Randal L. Schwartz [this message]
2005-11-01 21:52 ` Richard M. Stallman
2005-11-01 2:13 ` Richard M. Stallman
2005-11-02 8:01 ` Glenn Morris
2005-11-03 13:49 ` Richard M. Stallman
2005-11-04 18:12 ` Alfred M. Szmidt
2005-11-05 14:35 ` Richard M. Stallman
2005-11-05 15:27 ` Alfred M. Szmidt
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=86vezdlkke.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=emacs-devel@gnu.org \
--cc=piet@cs.uu.nl \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.