kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Questions about development-process
Date: Tue, 13 May 2014 00:29:41 +0200	[thread overview]
Message-ID: <20140512222941.GA5938@kroah.com> (raw)
In-Reply-To: <CANoiuGLtdjmNG=yYCJyPkW_1EM-e0WAEPtJHDmxwLr0ef8uWJg@mail.gmail.com>

On Sun, May 11, 2014 at 12:37:39PM -0700, David Matlack wrote:
> I have some questions after reading Documentation/development-process/.
> 
> 1. According to 2.Process, after the merge window closes...
> 
>      Over the next six to ten weeks, only patches which fix problems should
>      be submitted to the mainline.  On occasion a more significant change
>      will be allowed, but such occasions are rare; developers who try to
>      merge new features outside of the merge window tend to get an unfriendly
>      reception.
> 
> So is "submitting to mainline" == "sending patches to LKML"? I'm basically
> confused if the development process is talking about when to send patches or
> just when Linus will merge patches into his tree. (...or both?)

THe merge window is for kernel subsystem maintainers, as a "normal"
developer, you usually don't have to worry about that at all.

> 2. How does the development process apply to the staging directory? Can I send
> new features and bug fixes alike for drivers/staging/X at any time or should I
> separate out patches as:
>   - new features for drivers/staging/X sent only during merge window
>   - bug fixes sent whenever

You can send either whenever, and it's up to the maintainer as to when
to send them to Linus.  Hopefully the staging tree maintainer is smart
enough to know which to send to which :)

thanks,

greg k-h

      reply	other threads:[~2014-05-12 22:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11 19:37 Questions about development-process David Matlack
2014-05-12 22:29 ` Greg KH [this message]

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=20140512222941.GA5938@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).