Lines Matching refs:change

119 documentation) are greatly appreciated. Before making a large change, it is
120 usually a good idea to first open an issue describing the change to solicit
126 If the change being proposed alters code (as opposed to only documentation for
228 represent a single logical change, please squash those together.
239   * contain a short description of the change (preferably 50 characters or less,
308 squashed into one commit per logical change. Metadata will be added to the
342 Focus first on the most significant aspects of the change:
344 1. Does this change make sense for Tokio?
345 2. Does this change make Tokio better, even if only incrementally?
347 4. Is the commit message readable and correct? If it contains a breaking change
358 change over time. The first impression you give to a new contributor never does.
366 `Nit: change foo() to bar(). But this is not blocking.`
376 a particular change that makes `tonic` better, but the individual might