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: <m3hcqj6j2o.fsf@maximus.localdomain>
Date:	Sat, 12 May 2007 01:23:27 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Rene Herman <rene.herman@...il.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Rusty Russell <rusty@...tcorp.com.au>, bunk@...sta.de,
	randy.dunlap@...cle.com, akpm@...ux-foundation.org,
	rpjday@...dspring.com, marcel@...tmann.org, hch@...radead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] module_author: don't advice putting in an email address

Rene Herman <rene.herman@...il.com> writes:

> /* Author, ideally of form NAME <EMAIL>[, NAME <EMAIL>]*[ and NAME <EMAIL>]
>
> After my trivial patch, it says:
>
> /* Author, ideally of form NAME[, NAME]*[ and NAME] */

I think I would put something like this:

/* Author, of form NAME[, NAME]*[ and NAME]
 * If you have a permanent email address and are prepared for
   maintaining/supporting the module, you may want to provide
   the address as well */

The wording isn't the best I suppose.

I.e., the change would mean providing the address is not strictly
required and the person should think when adding it, that's all.
-- 
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