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: <m3fxvb9wuh.fsf@maximus.localdomain>
Date:	Sat, 01 Mar 2008 00:17:10 +0100
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Few ideas...

Jan Engelhardt <jengelh@...putergmbh.de> writes:

> d: I think it would not bad if it were included in the resulting
> object file like MODULE_AUTHOR is.

I specifically don't want it in the binary - maintainers change, it's
not a point of contact for end users. It would be for source code ops
only.

> If anything, MODULE_AUTHOR could be removed, because the original
> author(s) are usually listed at the top of the .c file and not
> always the ones to talk to when there is a bug (=> the maintainer
> is).

Perhaps it's there because of copyright.
-- 
Krzysztof Halasa
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ