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:	Wed, 25 May 2011 08:34:59 -0700
From:	Tony Lindgren <tony@...mide.com>
To:	Nicolas Pitre <nico@...xnic.net>
Cc:	Catalin Marinas <catalin.marinas@....com>,
	Arnd Bergmann <arnd@...db.de>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Russell King <linux@....linux.org.uk>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Marc Zyngier <marc.zyngier@....com>
Subject: Re: [RFC] ARM Subarchitecture group maintainership

* Nicolas Pitre <nico@...xnic.net> [110525 07:24]:
> 
> No.  We'll start merging stuff once this merge window is over.  In other 
> words, you are still on your own for the current one.

OK
 
> Also, I want stuff merged in this subarch tree way before the next merge 
> window opens on a continuous basis, not in a big rush before it opens, 
> or worse, while it is already open.

OK that sounds good to me. There's at least one more thing to sort out
though:

What do you want to do with with the various for-next branches?

Do you want to queue things into your tree before hitting for-next?

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