Lines Matching full:they

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