mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: tglx@linutronix.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
Subject: Re: [RFC 3/4] Documentation: Add cutoff periods for patch acceptance
Date: Mon, 15 Dec 2014 11:15:12 +0100	[thread overview]
Message-ID: <20141215101512.GB6444@pd.tnic> (raw)
In-Reply-To: <1418623790-28429-4-git-send-email-cernekee@gmail.com>

On Sun, Dec 14, 2014 at 10:09:49PM -0800, Kevin Cernekee wrote:
> This has been a recurring source of confusion for the new submitters who
> I've helped; let's see if adding a small illustration improves the
> situation.
> 
> Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
> ---
>  Documentation/development-process/5.Posting | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/Documentation/development-process/5.Posting b/Documentation/development-process/5.Posting
> index 14f8b01..50cf4dc 100644
> --- a/Documentation/development-process/5.Posting
> +++ b/Documentation/development-process/5.Posting
> @@ -35,6 +35,22 @@ merge window has closed.  You can visit https://www.kernel.org/ to check
>  the merge window status; it is closed if the "mainline:" entry shows a
>  version number containing "-rc", and open if a non-rc version number appears.
>  
> +In many cases, feature additions received and accepted somewhere in the range
> +of [N-rc1, N-rc5) will be merged into the -next tree targeting the (N+1) Linux
> +release.  For example:
> +
> +  kernel.org "mainline:"  |  Patch may appear
> +  field when posted       |  in released kernel
> +  ------------------------+--------------------------------
> +  3.18-rc[1-4]            |  3.19
> +  3.18-rc[5-9]            |  3.20
> +  3.18                    |  Merge window open - don't post
> +  3.19-rc[1-4]            |  3.20
> +  3.19-rc[5-9]            |  3.21
> +  3.19                    |  Merge window open - don't post
> +
> +Bug fixes can typically be accepted at any time.

Acked-by: Borislav Petkov <bp@suse.de>

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-12-15 10:15 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
2014-12-15  6:09 ` [RFC 3/4] Documentation: Add cutoff periods for patch acceptance Kevin Cernekee
2014-12-15 10:15   ` Borislav Petkov [this message]
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=20141215101512.GB6444@pd.tnic \
    --to=bp@alien8.de \
    --cc=akpm@linux-foundation.org \
    --cc=cernekee@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=corbet@lwn.net \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --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®