linux-kernel - Re: [PATCH v2 09/39] scripts/kernel-doc.py: add a Python parser

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: <87tt8hyedw.fsf@trenco.lwn.net>
Date: Tue, 25 Feb 2025 13:10:19 -0700
From: Jonathan Corbet <corbet@....net>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
 linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 09/39] scripts/kernel-doc.py: add a Python parser

Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:

> Em Mon, 24 Feb 2025 16:38:58 -0700
> Jonathan Corbet <corbet@....net> escreveu:
>
>> Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:
>> 
>> 
>> I also think you should give consideration to preserving the other
>> copyright notices in the Perl version.  A language translation doesn't
>> remove existing copyrights...who knows how much creativity went into
>> some of those regexes?
>
> Makes sense, but the copyrights at kernel-doc.pl:
>
> 	## Copyright (c) 1998 Michael Zucchi, All Rights Reserved        ##
> 	## Copyright (C) 2000, 1  Tim Waugh <twaugh@...hat.com>          ##
> 	## Copyright (C) 2001  Simon Huggins                             ##
> 	## Copyright (C) 2005-2012  Randy Dunlap                         ##
> 	## Copyright (C) 2012  Dan Luedtke                               ##
> 	##                                                               ##
> 	## #define enhancements by Armin Kuster <akuster@...sta.com>     ##
> 	## Copyright (c) 2000 MontaVista Software, Inc.                  ##
> 	#
> 	# Copyright (C) 2022 Tomasz Warniełło (POD)
>
> Also doesn't preserve all copyrights from people that worked hard to
> maintain it all over those years.

Agreed ... and I'm not sure what we can do about that.  But *removing*
existing copyright notices is a bit of a different story; that is
generally considered to be fairly bad form.

I don't have a problem with adding a longer credits area, I guess, if we
want to do that (though it's not normal for other source files).  But
I'm not sure we need to.

Thanks,

jon