All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Lafan Mining <lkfan@protonmail.com>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Re: Understanding merge window and next-tree
Date: Sat, 11 Sep 2021 10:16:45 +0200	[thread overview]
Message-ID: <YTxl7SWkctjd3Dmo@kroah.com> (raw)
In-Reply-To: <SJTHJLsPuI6MUCgu8X8-YjKt_hYqshM5ZP1AqOHnaotLURWehhK0gK2fGgOA-iN9ZFxuRNnoXJ9ERZ3LWqlGT12MyTkAh3v3ulmZaDyP_lw=@protonmail.com>

On Fri, Sep 10, 2021 at 04:06:39PM +0000, Lafan Mining wrote:
> I'm trying to understand how Linux Kernel development works and reading the relevant documentation at https://www.kernel.org/doc/html/latest/process/2.Process.html
> 
> So there is the so called next-tree accumulating all the patches from all the subsystems ready for merge and the mainline tree. The thing is the merge-window is opened for 2 weeks (as mentioned in the linked documentation) and as far as I understood all the changes will be merged into the mainline.
> 
> But looking through the next-tree I found some implementation in Rust https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/rust which is much older than 2 months.
> 
> How is that happened that after a few merge windows (4 if I counted correctly) it's still not merged?

Maintainers have to ask Linus to take their changes and be merged, Linus
does not directly merge from linux-next.  This allows for maintainers to
"skip" merge windows if needed, as well as have things in linux-next for
a long time before they go to Linus for various reasons (the -mm tree
has many such patches, and so does the rust tree as you have seen.)

So yes, the requirement is that changes have to be in linux-next before
it goes into Linus's tree, but it does not guarantee that anything is in
linux-next will end up in Linus's tree.

Does that help?

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2021-09-11  8:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10 16:06 Understanding merge window and next-tree Lafan Mining
2021-09-11  8:16 ` Greg KH [this message]
2021-09-11  8:40 ` Bernd Petrovitsch

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=YTxl7SWkctjd3Dmo@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=lkfan@protonmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.