From: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: emacs-devel@gnu.org
Subject: Re: Finish updating copyright years
Date: 30 Oct 2005 22:19:22 -0800 [thread overview]
Message-ID: <86ll0ap5sl.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <E1EWOG9-0006Xi-A9@fencepost.gnu.org>
>>>>> "Richard" == Richard M Stallman <rms@gnu.org> writes:
Richard> Would people please finish the updating the copyright years?
Richard> That is standing in the way of the release.
Just to make sure this is legal... the copyright year *cannot* change
unless something has changed (besides the copyright notice).
You can't take every file and just s/2004/2005/g, for example. You
can update the copyright if some change was actually made in the file.
It's conceivable, and in fact very likely, that some of the files
will still be copyright 2004 or earlier in this next release.
--
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 6:19 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 [this message]
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
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
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=86ll0ap5sl.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--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).