Lines Matching refs:patches

31 merging of patches for each release.  At the beginning of each development
36 this time, at a rate approaching 1,000 changes ("patches," or "changesets")
52 Over the next six to ten weeks, only patches which fix problems should be
86 serious.  For this reason, patches which cause regressions are looked upon
201 There is exactly one person who can merge patches into the mainline kernel
202 repository: Linus Torvalds.  But, of the over 9,500 patches which went
220 maintainers to track a list of patches, including authorship information
222 patches in his or her repository are not found in the mainline.
225 the patches they have selected for merging from their repositories.  If
226 Linus agrees, the stream of patches will flow up into his repository,
228 pays to specific patches received in a pull operation varies.  It is clear
230 trusts the subsystem maintainers to not send bad patches upstream.
232 Subsystem maintainers, in turn, can pull patches from other maintainers.
233 For example, the networking tree is built from patches which accumulated
240 Clearly, in a system like this, getting patches into the kernel depends on
241 finding the right maintainer.  Sending patches directly to Linus is not
247 The chain of subsystem trees guides the flow of patches into the kernel,
249 at all of the patches which are being prepared for the next merge window?
253 patches which use the older form of that function.  Reviewers and testers
262 started).  The -mm tree integrates patches from a long list of subsystem
263 trees; it also has some patches aimed at helping with debugging.
265 Beyond that, -mm contains a significant collection of patches which have
266 been selected by Andrew directly.  These patches may have been posted on a
271 patches which accumulate in -mm will eventually either be forwarded on to
273 development cycle, approximately 5-10% of the patches going into the
297 all patches merged during a given merge window should really have found
316 proper, as well as a list of people that should be Cc'd for any patches to
332 heavily on the ability to herd collections of patches in various
342 large repositories and large numbers of patches.  It also has a reputation
370 Some major subsystem maintainers use quilt to manage patches intended to go
461 some developers jump into the creation of patches fixing spelling errors or
462 minor coding style issues.  Unfortunately, such patches create a level of