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
93 serious.  For this reason, patches which cause regressions are looked upon
216 How patches get into the Kernel
219 There is exactly one person who can merge patches into the mainline kernel
220 repository: Linus Torvalds. But, for example, of the over 9,500 patches
238 maintainers to track a list of patches, including authorship information
240 patches in his or her repository are not found in the mainline.
243 the patches they have selected for merging from their repositories.  If
244 Linus agrees, the stream of patches will flow up into his repository,
246 pays to specific patches received in a pull operation varies.  It is clear
248 trusts the subsystem maintainers to not send bad patches upstream.
250 Subsystem maintainers, in turn, can pull patches from other maintainers.
251 For example, the networking tree is built from patches which accumulated
258 Clearly, in a system like this, getting patches into the kernel depends on
259 finding the right maintainer.  Sending patches directly to Linus is not
266 The chain of subsystem trees guides the flow of patches into the kernel,
268 at all of the patches which are being prepared for the next merge window?
272 patches which use the older form of that function.  Reviewers and testers
281 started).  The -mm tree integrates patches from a long list of subsystem
282 trees; it also has some patches aimed at helping with debugging.
284 Beyond that, -mm contains a significant collection of patches which have
285 been selected by Andrew directly.  These patches may have been posted on a
290 patches which accumulate in -mm will eventually either be forwarded on to
292 development cycle, approximately 5-10% of the patches going into the
312 all patches merged during a given merge window should really have found
332 proper, as well as a list of people that should be Cc'd for any patches to
349 heavily on the ability to herd collections of patches in various
359 large repositories and large numbers of patches.  It also has a reputation
387 Some major subsystem maintainers use quilt to manage patches intended to go
480 some developers jump into the creation of patches fixing spelling errors or
481 minor coding style issues.  Unfortunately, such patches create a level of