Lines Matching refs:patches

36 merging of patches for each release.  At the beginning of each development
41 this time, at a rate approaching 1,000 changes ("patches," or "changesets")
57 Over the next six to ten weeks, only patches which fix problems should be
92 serious.  For this reason, patches which cause regressions are looked upon
214 How patches get into the Kernel
217 There is exactly one person who can merge patches into the mainline kernel
218 repository: Linus Torvalds.  But, of the over 9,500 patches which went
236 maintainers to track a list of patches, including authorship information
238 patches in his or her repository are not found in the mainline.
241 the patches they have selected for merging from their repositories.  If
242 Linus agrees, the stream of patches will flow up into his repository,
244 pays to specific patches received in a pull operation varies.  It is clear
246 trusts the subsystem maintainers to not send bad patches upstream.
248 Subsystem maintainers, in turn, can pull patches from other maintainers.
249 For example, the networking tree is built from patches which accumulated
256 Clearly, in a system like this, getting patches into the kernel depends on
257 finding the right maintainer.  Sending patches directly to Linus is not
264 The chain of subsystem trees guides the flow of patches into the kernel,
266 at all of the patches which are being prepared for the next merge window?
270 patches which use the older form of that function.  Reviewers and testers
279 started).  The -mm tree integrates patches from a long list of subsystem
280 trees; it also has some patches aimed at helping with debugging.
282 Beyond that, -mm contains a significant collection of patches which have
283 been selected by Andrew directly.  These patches may have been posted on a
288 patches which accumulate in -mm will eventually either be forwarded on to
290 development cycle, approximately 5-10% of the patches going into the
310 all patches merged during a given merge window should really have found
330 proper, as well as a list of people that should be Cc'd for any patches to
347 heavily on the ability to herd collections of patches in various
357 large repositories and large numbers of patches.  It also has a reputation
385 Some major subsystem maintainers use quilt to manage patches intended to go
478 some developers jump into the creation of patches fixing spelling errors or
479 minor coding style issues.  Unfortunately, such patches create a level of