Lines Matching full:changes
19 internal API changes, and more. A typical release can contain about 13,000
20 changesets with changes to several hundred thousand lines of code. Recent
34 community) is merged into the mainline kernel. The bulk of changes for a
35 new development cycle (and all of the major changes) will be merged during
36 this time, at a rate approaching 1,000 changes ("patches," or "changesets")
39 (As an aside, it is worth noting that the changes integrated during the
96 worse; the pile of changes waiting for the next merge window will grow
145 and controversial changes, go on for years. Much developer frustration
178 getting feedback about changes that are needed, you should either
179 make those changes or justify why they should not be made. If your
197 problems caused by API changes. But the original developer should
259 Developers will be interested in what other changes are pending to see
260 whether there are any conflicts to worry about; a patch which changes a
263 want access to the changes in their integrated form before all of those
264 changes land in the mainline kernel. One could pull changes from all of
376 toward tracking a specific set of changes against an evolving code base.