Lines Matching refs:patch
8 - Creates patch directly from your branch
19 It is intended to automate patch creation and make it a less
26 git format-patch, git send-email, etc. with the correct parameters
42 - Maintain a number of branches, one for each patch series you are
146 This will create patch files in your current directory and tell you who
147 it is thinking of sending them to. Take a look at the patch files.
173 Email address / alias to send patch series to (you can add this
177 Email address / alias to Cc patch series to (you can add this
181 Sets the version number of this patch series
185 RFC patches, or RESEND if you are being ignored. The patch subject
189 the patch shows like: [InternalProject][RFC/RESEND PATCH]
199 URL you want is the one for the series itself, not any particular patch.
218 This is the patch set title
234 Sets some notes for the patch series, which you don't want in
244 Similar, but for a single commit (patch). These notes will appear
245 immediately below the --- cut in the patch file.
256 These indicate that someone has tested/reviewed/acked your patch.
295 This copies a single patch to another email address. Note that the
316 (but logically the same patch) as other patches that have been
329 patch series and see how the patches turn out.
354 will create a patch which is copied to x86, arm, sandbox, mikef, ag and
381 and patman will show you each patch and what review tags have been collected,
393 This shows that patch 21 and 22 were sent out with one review but have since
411 There is also a -C option to list the comments received for each patch.
431 The first patch is some test things that enable your code to be compiled,
432 but that you don't want to submit because there is an existing patch for it
434 (skipping the first patch) with:
443 Let's say that patman reports an error in the second patch. Then:
451 Now you have an updated patch series. To check it:
495 Let's say one person sent comments and you get an Acked-by: on one patch.
496 Also, the patch on the list that you were waiting for has been merged,
589 not later when you can't remember which patch you changed. You can always
599 change. For clarity, if there are no changes for this patch in the most
600 recent revision of the series, a note will be added. For example, a patch