3 ms·
a more interesting treatment of the topic by the author of curl is here: https://daniel.haxx.se/blog/2023/01/08/copyright-without-years/ https://daniel.haxx.se/
by em-bee 4y ago
a more interesting treatment of the topic by the author of curl is here: https://daniel.haxx.se/blog/2023/01/08/copyright-without-years/ https://daniel.haxx.se/blog/2023/01/08/copyright-without-yea...
including an opposing view which suggests to include the original year and keep that:
https://liferay.dev/blogs/-/blogs/how-and-why-to-properly-write-copyright-statements-in-your-code#why-keep-the-year https://liferay.dev/blogs/-/blogs/how-and-why-to-properly-wr...
mainly for this reason:
having an easy way to find the earliest date of a piece of code, might prove useful also in figuring out when an invention was first expressed to the general public. Something that might become useful for patent defense
so while updating the year does not seem very useful, knowing when a file was created is much more useful.
- vlovich123 4y agogit log —follow is probably a more reliable mechanism to answer that in practice.
- nequo 4y agoWouldn’t a VCS be more useful for patent disputes as it keeps more fine-grained track of what changed in the source code and when?