Re: Copyyear statement astonishing to me

[bendikker]

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.
https://git.savannah.gnu.org/cgit/coreutils.git/commit/src/ptx.c?id=7b0caffd312443449cb1f398ded7104794e1dc69
https://git.savannah.gnu.org/cgit/coreutils.git/tree/src/ptx.c

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!