linux-kernel - Re: [RFC 2/4] Documentation/SubmitChecklist: Remind submitters to check the merge window

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:	Tue, 16 Dec 2014 08:48:33 +0200
From:	Kalle Valo <kvalo@...rom.com>
To:	Kevin Cernekee <cernekee@...il.com>
Cc:	tglx@...utronix.de, bp@...en8.de, gnomes@...rguk.ukuu.org.uk,
	computersforpeace@...il.com, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, corbet@....net,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Johannes Berg <johannes@...solutions.net>
Subject: Re: [RFC 2/4] Documentation/SubmitChecklist: Remind submitters to check the merge window

Kevin Cernekee <cernekee@...il.com> writes:

> +27: For patches which are not urgent fixes for bugs in the current tree,
> +    double-check https://www.kernel.org/ to make sure the merge window is
> +    CLOSED ("mainline:" showing an -rc kernel) before sending.  For more
> +    information on the release cycle, see Documentation/development-process/.

Maybe the crystal ball should be extended to show if the merge is open
or closed? And if it's closed, an estimate when the next merge window
starts would be nice ("Merge window is closed, estimate for it to open:
21 days").

http://phb-crystal-ball.org/

I'm sure Johannes would be happy to take patches.

-- 
Kalle Valo
--
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/