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] [day] [month] [year] [list]
Date:	Sun, 4 May 2008 17:56:12 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: charter for -next

Hi Stefan,

On Sat, 03 May 2008 12:12:50 +0200 Stefan Richter <stefanr@...6.in-berlin.de> wrote:
>
> What should I ask myself before I commit something to the branch which 
> Stephen pulls into -next?
> 
>      Is this ready to be pulled by Linus right now if he had a merge
>      window open today?

This is what I want ideally.  So as stuff stabilises in subsystem trees,
it can be incorporated into linux-next and we can then figure out the
problems introduced by interactions with other subsystems.

>      Is it likely that I will let Linus pull this when he opens his next
>      merge window?  (Assuming I can roughly predict when this will be,
>      and what other work will likely be done until then, e.g. pending
>      reviewer feedback, or patches for related functionality which should
>      be bundled with the work in question...)

I suspect that this is what I got in some cases during the last
cycle :-) :-(

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ