-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Wildenhues on 1/12/2006 12:43 AM: >> >>Isn't this a question of Copyright law, which easily trounces >>--version? > > > Correct. Please pretend I never wrote that sentence; all files in > question will definitely have relevant changes before the next release, > and those changes will happen this year.
Furthermore, the GNU coding standards were recently updated, and http://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices now states "To update the list of year numbers, add each year in which you have made nontrivial changes to the package. (Here we assume you're using a publicly accessible revision control server, so that every revision installed is also immediately and automatically published.) When you add the new year, it is not required to keep track which files have seen significant changes in the new year and which have not. It is recommended and simpler to add the new year to all files in the package, and be done with it for the rest of the year." So I think it might even be okay for a blanket addition of 2006 to every file in libtool that carries a copyright disclaimer, whether or not the file ends up being edited this year. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDx68L84KuGfSFAYARAq7kAJ4w2jyelHmtfu/FtJaxOlXqcGemZACgppMM Z11/GL1hL9Dr00oRUDVIaWk= =URBt -----END PGP SIGNATURE-----