linux-kernel - Re: [1/7] Documentation: Add license-rules.rst to describe how to properly identify file licenses

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: <alpine.DEB.2.20.1711131324170.1851@nanos>
Date:   Mon, 13 Nov 2017 13:26:06 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Charlemagne Lasse <charlemagnelasse@...il.com>
cc:     LKML <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...uxfoundation.org>,
        Andrew Morton <akpm@...uxfoundation.org>,
        Jonathan Corbet <corbet@....net>,
        Philippe Ombredanne <pombredanne@...b.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Christoph Hellwig <hch@....de>,
        Russell King <rmk+kernel@...linux.org.uk>,
        Rob Herring <rob.herring@...aro.org>,
        Jonas Oberg <jonas@...e.org>, Joe Perches <joe@...ches.com>,
        linux-xfs@...r.kernel.org,
        Kate Stewart <kstewart@...uxfoundation.org>,
        Carmen Bianca Bakker <carmenbianca@...e.org>
Subject: Re: [1/7] Documentation: Add license-rules.rst to describe how to
 properly identify file licenses

On Mon, 13 Nov 2017, Charlemagne Lasse wrote:
> > +If a specific tool cannot handle the standard comment style, then the
> > +appropriate comment mechanism which the tool accepts shall be used.
> 
> Most of the things sound good. But I really don't get the first-line
> thing and the C++ single line comments in C sources.

That's been a decision from Linus and probably not going to change, even if
you argue in circles.

Thanks,

	tglx