From: Kalle Valo <kvalo@adurom.com>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: tglx@linutronix.de, bp@alien8.de, gnomes@lxorguk.ukuu.org.uk,
computersforpeace@gmail.com, torvalds@linux-foundation.org,
akpm@linux-foundation.org, corbet@lwn.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [RFC 2/4] Documentation/SubmitChecklist: Remind submitters to check the merge window
Date: Tue, 16 Dec 2014 08:48:33 +0200 [thread overview]
Message-ID: <87iohc2ipq.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1418623790-28429-3-git-send-email-cernekee@gmail.com> (Kevin Cernekee's message of "Sun, 14 Dec 2014 22:09:48 -0800")
Kevin Cernekee <cernekee@gmail.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
next prev parent reply other threads:[~2014-12-16 7:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 6:09 [RFC 0/4] Stop maintainer abuse Kevin Cernekee
2014-12-15 6:09 ` [RFC 1/4] Documentation: Change policy on sending patches during merge window Kevin Cernekee
2014-12-15 8:29 ` Christoph Hellwig
2014-12-15 6:09 ` [RFC 2/4] Documentation/SubmitChecklist: Remind submitters to check the " Kevin Cernekee
2014-12-15 10:17 ` Borislav Petkov
2014-12-16 6:48 ` Kalle Valo [this message]
2014-12-15 6:09 ` [RFC 3/4] Documentation: Add cutoff periods for patch acceptance Kevin Cernekee
2014-12-15 10:15 ` Borislav Petkov
2014-12-15 14:59 ` One Thousand Gnomes
2014-12-15 18:29 ` Linus Torvalds
2014-12-15 6:09 ` [RFC 4/4] Documentation: Provide suggestions on when to repost patches Kevin Cernekee
2014-12-15 10:13 ` Borislav Petkov
2014-12-16 18:09 ` [RFC 0/4] Stop maintainer abuse Jonathan Corbet
2014-12-16 20:35 ` Theodore Ts'o
2014-12-16 22:19 ` Kevin Cernekee
2014-12-16 22:31 ` Borislav Petkov
2014-12-17 5:14 ` Theodore Ts'o
2014-12-17 9:52 ` Borislav Petkov
2014-12-18 19:05 ` Mark Brown
2014-12-18 10:35 ` Paolo Bonzini
2014-12-18 10:42 ` Borislav Petkov
2014-12-18 10:53 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iohc2ipq.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=corbet@lwn.net \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=johannes@sipsolutions.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®