Lines Matching refs:merge

37 cycle, the "merge window" is said to be open.  At that time, code which is
45 merge window do not come out of thin air; they have been collected, tested,
49 The merge window lasts for approximately two weeks.  At the end of this
52 for example, the release which happens at the end of the merge window will
54 merge new features has passed, and that the time to stabilize the next
59 allowed, but such occasions are rare; developers who try to merge new
60 features outside of the merge window tend to get an unfriendly reception.
61 As a general rule, if you miss the merge window for a given feature, the
78 	February 11	4.16-rc1, merge window closes
100 worse; the pile of changes waiting for the next merge window will grow
217 There is exactly one person who can merge patches into the mainline kernel
240 When the merge window opens, top-level maintainers will ask Linus to "pull"
266 at all of the patches which are being prepared for the next merge window?
303 the mainline is expected to look like after the next merge window closes.
310 all patches merged during a given merge window should really have found
311 their way into linux-next some time before the merge window opens.