Lines Matching full:patch

9 what part is affected by the patch followed by one sentence that
19 same file(s) as the patch being sent.
21 The body of the commit message should describe what the patch changes
34 email address.  If you're not the patch's original author, you should
35 also gather S-o-b's by them (and/or whomever gave the patch to you.) The
36 significance of this is that it certifies that you created the patch,
55 If a patch is not found in Patchwork, there is a high possibility for it to be
60 When you send a revised version of a patch, it would be very nice to mark your
61 old patch as superseded (or rejected, if that is applicable). You can change
63 identified by email address you use to register. Updating your patch status
66 The following patch states are found in Patchwork:
75 	The patch is merged in the master branch upstream, as is or slightly
80 	the patch.
86 	The email was not actually a patch, or the patch is not for Wayland or
92 	Reviewers determined that changes to the patch are needed. The
94 	not wait for your patch to be set to this state before revising,
98 	Mostly unused as the patch is waiting for upstream actions but
103 	A revised version of the patch has been submitted.