Lines Matching refs:merge

32 cycle, the "merge window" is said to be open.  At that time, code which is
40 merge window do not come out of thin air; they have been collected, tested,
44 The merge window lasts for approximately two weeks.  At the end of this
47 for example, the release which happens at the end of the merge window will
49 merge new features has passed, and that the time to stabilize the next
54 allowed, but such occasions are rare; developers who try to merge new
55 features outside of the merge window tend to get an unfriendly reception.
56 As a general rule, if you miss the merge window for a given feature, the
72 	January 18	2.6.38-rc1, merge window closes
94 worse; the pile of changes waiting for the next merge window will grow
201 There is exactly one person who can merge patches into the mainline kernel
224 When the merge window opens, top-level maintainers will ask Linus to "pull"
249 at all of the patches which are being prepared for the next merge window?
286 the mainline is expected to look like after the next merge window closes.
293 all patches merged during a given merge window should really have found
294 their way into linux-next some time before the merge window opens.