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]
Date:	Mon, 13 Aug 2007 16:16:30 -0400
From:	Theodore Tso <tytso@....edu>
To:	Krzysztof Halasa <khc@...waw.pl>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	Mariusz Kozlowski <m.kozlowski@...land.pl>,
	Joe Perches <joe@...ches.com>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl

On Mon, Aug 13, 2007 at 08:41:03PM +0200, Krzysztof Halasa wrote:
> Arjan van de Ven <arjan@...radead.org> writes:
> 
> > The maintainer info should be in the source file itself!
> 
> Nope, it should be outside of the (downloadable) tarball, because
> once someone get a tarball you can't update the data in it.
> This is fine WRT source (which is static given a version) but
> doesn't work for fast-changing data.

But the maintainers file is in the tarball today.  If someone wants to
take the information from the latest git tree, gather it up into a
single html file, and put it on the web, more power to them.  But it
seems that the master source of the data should be the source file.

      	       	      	     	    - Ted
-
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