Lines Matching full:development

17 development history.  Indeed, given the scale of the project, avoiding
42 Used properly, rebasing can yield a cleaner and clearer development
73    between release points; basing development on one of those points
97 Merging is a common operation in the kernel development process; the 5.1
98 development cycle included 1,126 merge commits - nearly 9% of the total.
128 branches.  Failure to do so threatens the security of the development
145 sure that there are no conflicts with parallel development and generally
149 Why is that?  Back merges will muddy the development history of your own
153 also obscure problems with the development process in your tree; they can
171 in the 5.1 development cycle) and has gotten quite good at conflict
203 commits for one development cycle so that those changes have time to
210 the development cycle in order to pick up changes and fixes done elsewhere