Lines Matching full:they

40 merge window do not come out of thin air; they have been collected, tested,
58 exception is made for drivers for previously-unsupported hardware; if they
59 touch no in-tree code, they cannot cause regressions and should be safe to
125 Some kernels are designated "long term" kernels; they will receive support
163    developers on that list reply with any comments they may have.  This
179    make those changes or justify why they should not be made.  If your
222 of the kernel they manage; they are the ones who will (usually) accept a
233 the patches they have selected for merging from their repositories.  If
276 mailing list, or they may apply to a part of the kernel for which there is
297 lists when they are assembled; they can be downloaded from:
311 being added to the kernel tree live.  They remain in drivers/staging while
312 they still need more work; once complete, they can be moved into the
327 where, with luck, they will come to the attention of other developers and
352 developers; even if they do not use it for their own work, they'll need git
474 increasingly, they are looked down upon.  New developers wishing to
476 they wish for by these means.