Lines Matching full:changes
25 <li><a href="#attribution">Attribution of Changes</a></li>
91 Reading the "commits" list and paying attention to changes being made by
117 patches may not apply correctly if the underlying code changes between the
125 <tt>configure</tt> script, please separate out those changes into
126 a separate patch from the rest of your changes.</li>
132 sends it (e.g. by making whitespace changes or by wrapping lines).</p>
150 <li>All developers are required to have significant changes reviewed before
157 major changes to be reviewed before being committed, but smaller changes
158 (or changes where the developer owns the component) can be reviewed after
162 all necessary review-related changes.</li>
284 the change (more invasive changes require more testing). A reasonable
295 <li>The changes should not cause any correctness regressions in the
302 <li>The changes should not cause performance or correctness regressions in
366 reverting obviously broken patches, documentation/comment changes, any
367 other minor changes.</li>
379 <p>In any case, your changes are still subject to <a href="#reviews">code
394 <li>keep the community informed about future changes to LLVM, </li>
410 done as a series of <a href="#incremental">incremental changes</a>, not as a
417 <p>In the LLVM project, we do all significant changes as a series of incremental
418 patches. We have a strong dislike for huge changes or long-term development
428 <li>Huge changes (produced when a branch is merged back onto mainline) are
434 <li>Changes developed as monolithic large changes often don't work until the
435 entire set of changes is done. Breaking it down into a set of smaller
436 changes increases the odds that any of the work will be committed to the
445 <li>Large/invasive changes usually have a number of secondary changes that are
447 sorts of changes can often be done before the major change is done,
451 of changes if possible. Once this is done, define the first increment and
455 a planned series of changes that works towards the development goal.</li>
476 <h3><a name="attribution">Attribution of Changes</a></h3>
599 for patent-related trouble with their changes. If you or your employer own
