Lines Matching refs:changes
25 API changes, and more. A typical 2.6 release can contain nearly 10,000
26 changesets with changes to several hundred thousand lines of code. 2.6 is
28 rolling development model which is continually integrating major changes.
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
94 worse; the pile of changes waiting for the next merge window will grow
137 and controversial changes, go on for years. Much developer frustration
170 getting feedback about changes that are needed, you should either
171 make those changes or justify why they should not be made. If your
189 problems caused by API changes. But the original developer should
250 Developers will be interested in what other changes are pending to see
251 whether there are any conflicts to worry about; a patch which changes a
254 want access to the changes in their integrated form before all of those
255 changes land in the mainline kernel. One could pull changes from all of
365 toward tracking a specific set of changes against an evolving code base.