[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Copyyear statement astonishing to me

From: bendikker
Subject: Re: Copyyear statement astonishing to me
Date: Sat, 29 Dec 2018 15:14:44 +0000
User-agent: Horde Application Framework 5

If that is the rule, than I will have to except.

But it stays confusing, because one file excists in many places
and the only difference between them is the copyright years.

You can also remove all years, accept the first?
Than you always use year-year.

The following is one such example.

Personaly I would only add a copyright year if I changed a file, unless that is legaly no good.
(Althoug, I have no programming skills.)

Quoting "Alfred M. Szmidt" <address@hidden>:

Please take some effort into trying to make clear what the confusion
is for you.

   false --> 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.

That is what the GNU Coding Standards say, so it clearly is not "false".

If you add a new file, from a different project, which was not updated

this year, then you would add 2018 in your new copy of that file.
Adding a new file is a signitificant enough modification that it would
warrant updating the copyright years for _all_ files in the project;
including newly added ones.


ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]