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>] [day] [month] [year] [list]
Message-ID: <20080927221313.GA24032@informatik.uni-freiburg.de>
Date:	Sun, 28 Sep 2008 00:13:14 +0200
From:	Uwe Kleine-König 
	<ukleinek@...ormatik.uni-freiburg.de>
To:	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: reformating of MAINTAINERS

Hello,

I rebased my changes to MAINTAINERS to Linus' current HEAD.  In the
meantime I'm not convinced anymore that restoring the alphabetic
ordering is still worth the effort[1] because I work on decentralizing
the info contained in that file.  But I still think that merging P and M
is sensible.  So I changed the order of my commits to have the
alphabetic order commit the topmost one.

So now there are two branches, maintainers and maintainers-fixes that
only differ in that one commit.

	git://git.breakpoint.cc/ukleinek/linux-2.6 maintainers

resp.

	git://git.breakpoint.cc/ukleinek/linux-2.6 maintainers-alphabetic

It's gitweb browsable at 

	http://git.breakpoint.cc/cgi-bin/gitweb.cgi?p=ukleinek/linux-2.6;a=summary

@Linus:  Do you like it?  Do you consider pulling in the merge window?

Best regards
Uwe

[1] I don't mean to actually fix the ordering, because this is done by
an already existing script, but it might result in merge conflicts.

-- 
Uwe Kleine-König

Set the I_WANT_A_BROKEN_PS environment variable to force BSD syntax ...
	-- manpage of procps
--
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