[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fri, 28 Jan 2011 01:51:29 GMT
whereas the latter is literally copied into
other .h files and therefore does not have a copyright notice
Having a file in a public repo is legally a kind of distribution.
(This is why we're able to increment years in copyright notices on Jan 1,
for those who like to do so. :)
So the files, like all files, should have some kind of copyright
statement. It could be in an accompanying README rather than in the
would be possibly legally confusing if a file has two copyright notices
It's only confusing if the notices conflict. In which case there is a
real problem. Not having a notice on a file doesn't eliminate such a
problem, it just obscures it.