Lines Matching full:changes

82 resolving conflicts and dealing with API changes.
84 Only the most simple changes should be formatted as a single patch;
85 everything else should be made as a logical series of changes.  Splitting
91    changes found in your working revision control system.  Instead, the
92    changes you have made need to be considered in their final form, then
94    discrete, self-contained changes, not the path you took to get to those
95    changes.
98    patch.  These changes can be small ("add a field to this structure") or
105    changes in the same patch.  If a single patch fixes a critical security
186 support other changes coming in later patch, say so.  If internal APIs are
187 changed, detail those changes and how other developers should respond.  In
196    option to diff will associate function names with changes, making the
293    which have had gratuitous white-space changes or line wrapping performed