linux-kernel - Kernel GPLv question-"Prominent Notice"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100728231017.GA23605@dvomlehn-lnx2.corp.sa.net>
Date:	Wed, 28 Jul 2010 16:10:17 -0700
From:	David VomLehn <dvomlehn@...co.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Kernel GPLv question-"Prominent Notice"

Not looking to be flamed, but I gotta ask. The GPLv2 has the sentence:

	You must cause the modified files to carry prominent notices
	stating that you changed the files and the date of any change.

My understanding of kernel community protocol is that you only put change
info in the source file if you made a major change, not if you corrected
something minor. IIRC, I even saw a patch bounced, in part, because it had
a line of change info added for a minor fix. (Again, IIRC, it was accepted
when it was resubmitted as modified)

We've been sued a time or two, making our legal folk a bit sensitive and
they want developers to follow the GPL to the letter. Now, they're not
likely to post anything here, but I thought I might personally get some
sense of what the future might hold. And I'm confident I can look
forward to some clearly stated viewpoints.
-- 
David VL
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/