Mercurial > emacs
view admin/notes/years @ 83307:21eea50897a7
Merged from miles@gnu.org--gnu-2005 (patch 69, 313-319)
Patches applied:
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-313
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-314
Merge from gnus--rel--5.10
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-315
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-316
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-317
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-318
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-319
Update from CVS
* miles@gnu.org--gnu-2005/gnus--rel--5.10--patch-69
Update from CVS
git-archimport-id: lorentey@elte.hu--2004/emacs--multi-tty--0--patch-347
author | Karoly Lorentey <lorentey@elte.hu> |
---|---|
date | Fri, 20 May 2005 17:44:36 +0000 |
parents | fc472d032079 |
children | 344e02ca2730 |
line wrap: on
line source
How to Maintain Copyright Years for GNU Emacs Principle: Individual files need to have the year of the release in the copyright notice if there is significant change. Practice: - individual files - each must be examined, along w/ its history, by a human - automated tools facilitate but can never replace this process - year of the release - may be different from year of file introduction, or year of last significant change - sometimes the release year slips, leaving a file w/ prematurely marked release year => need update (e.g., s/2004/2005/ for Emacs 22) - intervening years (between releases) are not valid and may cause embarrassment later in case of dispute => remove (however, see next) - years for new files (merged, contributed) that have been separately published are valid even if between releases => leave alone - significant change - insignificant - whitespace - copyright notice - version control tags - simple var/func renaming - in-file reorganization/reordering - typos - small bugfixes - small docfixes - filename renaming - most everything else is significant - change to interface - change in functionality - new file - many small changes may be significant in aggregate - when in doubt, ask (and update these guidelines -- thanks!) - sometimes people make mistakes - if they have not read these guidelines, point them here - if the guidelines are not helpful, improve the guidelines