linux-kernel - Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d120d5000706150930g5768f07fw33d9f5ab0275ce9f@mail.gmail.com>
Date:	Fri, 15 Jun 2007 12:30:54 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc:	"Daniel Forrest" <forrest@...g.wisc.edu>,
	"Bernd Paysan" <bernd.paysan@....de>,
	"Alexandre Oliva" <aoliva@...hat.com>,
	"Paulo Marques" <pmarques@...popie.com>,
	"Al Viro" <viro@....linux.org.uk>,
	"Krzysztof Halasa" <khc@...waw.pl>, linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On 6/15/07, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> > But that begs the question: How do you know what has been modified so
> > you can revert the modifications?  There won't necessarily be any
> > indication of which files have been modified.
>
> There will
>
> 2a) You must cause the modified files to carry prominent notices
>    stating that you changed the files and the date of any change.
>

So how do you deduce what to revert (without going upstream for a
pristine copy) if you see the following notice (I assume it is
prominent enough):
:

/*
 * ATTENTION!!!
 * This file was modified from it's original version on 30-FEB-2345 by XYZ
 */

?

-- 
Dmitry
-
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/