linux-kernel - Re: linux-next: rebase of the jdelvare-hwmon quilt series

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]

Message-Id: <20130712103601.69fe5dd208fa562944a8af10@canb.auug.org.au>
Date:	Fri, 12 Jul 2013 10:36:01 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Paul Gortmaker <paul.gortmaker@...il.com>
Cc:	Jean Delvare <khali@...ux-fr.org>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: linux-next: rebase of the jdelvare-hwmon quilt series

On Fri, 12 Jul 2013 10:27:59 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> As Paul said, new material should not enter linux-next until after -rc1
> is released.  In fact, every time Linus opens a merge window, I send an
> email to lkml and the linux-next list saying just that.  I also often add
> that message to the top of my daily release announcements (though I
> forgot during this merge window).
> 
> This restriction is imposed so that maintainers still getting their code
> into the current merge window are not distracted by reports of problems
> in linux-next to do with code that will not be merged in this merge
> window.

Of course, this does not apply to bug fixes etc.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped