Lines Matching refs:patch
16 * A patch that is generally in good shape and that was submitted while the
53 Also the review often happens not immediately after a patch was submitted,
76 Sometimes it is not clear if a patch contains a bug fix or not.
94 cleanup and submits the patch a couple of hours late, instead of
95 submitting a green patch which will waste efforts from several people
123 feedback to the submitter of a patch about what is going on: if the
124 patch was accepted, or if it was rejected (which exact list of
128 patch, these should leave no doubt if they were just comments and the
129 patch will be accepted anyway, or if the patch should be
149 of the patch and that they accept the `Developer Certificate of Origin
155 just pass on a patch without any changes.
168 * Reviewed-by: The patch has been reviewed and found acceptable according to
171 A *Reviewed-by:* tag is a statement of opinion that the patch is an
174 *Reviewed-by:* tag for a patch.
177 handling of a patch but wishes to signify and record their approval of it
178 then they can arrange to have an *Acked-by:* line added to the patch's
181 * Tested-by: A *Tested-by:* tag indicates that the patch has been successfully
188 * Reported-by: If this patch fixes a problem reported by somebody else,
194 * Cc: If a person should have the opportunity to comment on a patch, you may
195 optionally add a *Cc:* tag to the patch. Git tools (git send-email) will then
196 automatically arrange that they receives a copy of the patch when you submit
209 #. The responsible custodian inspects this patch, especially for:
218 * The patch fixes a real problem.
220 * The patch does not introduce new problems, especially it does not break
226 a "best effort" if a patch does not apply cleanly, but can be made to apply
228 patch must be against. It is acceptable to request patches against the
232 the custodian or too much work on an individual submitting a patch when
239 processing the patch should follow up to the email saying they intend to
245 #. The final decision to accept or reject a patch comes down to the custodian
248 #. If accepted, the custodian adds the patch to their public git repository.