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
127 Some kernels are designated "long term" kernels; they will receive support
171 developers on that list reply with any comments they may have. This
187 make those changes or justify why they should not be made. If your
230 of the kernel they manage; they are the ones who will (usually) accept a
241 the patches they have selected for merging from their repositories. If
284 mailing list, or they may apply to a part of the kernel for which there is
305 lists when they are assembled; they can be downloaded from:
319 being added to the kernel tree live. They remain in drivers/staging while
320 they still need more work; once complete, they can be moved into the
335 where, with luck, they will come to the attention of other developers and
360 developers; even if they do not use it for their own work, they'll need git
481 increasingly, they are looked down upon. New developers wishing to
483 they wish for by these means.