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
209 How patches get into the Kernel
212 There is exactly one person who can merge patches into the mainline kernel
213 repository: Linus Torvalds. But, for example, of the over 9,500 patches
231 maintainers to track a list of patches, including authorship information
233 patches in his or her repository are not found in the mainline.
236 the patches they have selected for merging from their repositories.  If
237 Linus agrees, the stream of patches will flow up into his repository,
239 pays to specific patches received in a pull operation varies.  It is clear
241 trusts the subsystem maintainers to not send bad patches upstream.
243 Subsystem maintainers, in turn, can pull patches from other maintainers.
244 For example, the networking tree is built from patches which accumulated
251 Clearly, in a system like this, getting patches into the kernel depends on
252 finding the right maintainer.  Sending patches directly to Linus is not
259 The chain of subsystem trees guides the flow of patches into the kernel,
261 at all of the patches which are being prepared for the next merge window?
265 patches which use the older form of that function.  Reviewers and testers
274 started).  The -mm tree integrates patches from a long list of subsystem
275 trees; it also has some patches aimed at helping with debugging.
277 Beyond that, -mm contains a significant collection of patches which have
278 been selected by Andrew directly.  These patches may have been posted on a
283 patches which accumulate in -mm will eventually either be forwarded on to
285 development cycle, approximately 5-10% of the patches going into the
305 all patches merged during a given merge window should really have found
325 proper, as well as a list of people that should be Cc'd for any patches to
342 heavily on the ability to herd collections of patches in various
352 large repositories and large numbers of patches.  It also has a reputation
380 Some major subsystem maintainers use quilt to manage patches intended to go
440   :ref:`Documentation/process/submitting-patches.rst <interleaved_replies>`.
474 some developers jump into the creation of patches fixing spelling errors or
475 minor coding style issues.  Unfortunately, such patches create a level of