From: Richard Stallman <rms@gnu.org>
Cc: teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: Years in copyright notices
Date: Thu, 24 Jun 2004 19:48:05 -0400 [thread overview]
Message-ID: <E1Bddwr-0002aE-A2@fencepost.gnu.org> (raw)
In-Reply-To: <445E1C12-C4E4-11D8-86C1-000D93505B76@swipnet.se> (jan.h.d@swipnet.se)
What is a "small change", 3-4 lines changed? And do many small changes
eventually become a big change that needs to change the year?
I think the threshold should be 10 lines of new code, the same as the
threshold for needing legal papers. If over 10 to 15 lines of new
code have been introduced in a file during a year, that year should be
mentioned.
This is the situation now that we have an accessible CVS repository,
so that every version of every file is always released. In the past,
the situation was different; years in which there was no release did
not count, and the changes in those years all counted towards the year
of the following release.
Is it enough to compare the file now with the version for the previous
year and count changed and added lines,
It would do no harm to handle it this way.
next prev parent reply other threads:[~2004-06-24 23:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 5:08 Years in copyright notices Richard Stallman
2004-06-17 13:13 ` Kim F. Storm
2004-06-18 2:42 ` Miles Bader
2004-06-18 21:51 ` Richard Stallman
2004-06-21 20:46 ` Luc Teirlinck
2004-06-22 5:18 ` Eli Zaretskii
2004-06-22 23:17 ` Richard Stallman
2004-06-23 7:09 ` Jan D.
2004-06-24 23:48 ` Richard Stallman [this message]
2004-06-23 8:08 ` Kim F. Storm
2004-06-23 8:22 ` Miles Bader
2004-06-23 9:58 ` Kim F. Storm
2004-06-24 23:48 ` Richard Stallman
2004-06-25 0:03 ` Miles Bader
2004-06-23 22:39 ` Kevin Ryde
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=E1Bddwr-0002aE-A2@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=teirllm@dms.auburn.edu \
/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.