Lines Matching refs:patch

10 - Creates patch directly from your branch
16 It is intended to automate patch creation and make it a less
23 git format-patch, git send-email, etc. with the correct parameters
39 - Maintain a number of branches, one for each patch series you are
141 This will create patch files in your current directory and tell you who
142 it is thinking of sending them to. Take a look at the patch files.
168 	Email address / alias to send patch series to (you can add this
172 	Email address / alias to Cc patch series to (you can add this
176 	Sets the version number of this patch series
180 	RFC patches, or RESEND if you are being ignored. The patch subject
184 	the patch shows like: [InternalProject][RFC/RESEND PATCH]
192 This is the patch set title
208 	Sets some notes for the patch series, which you don't want in
218 	Similar, but for a single commit (patch). These notes will appear
219 	immediately below the --- cut in the patch file.
230 	These indicate that someone has tested/reviewed/acked your patch.
252 	This copies a single patch to another email address. Note that the
274 patch series and see how the patches turn out.
299 will create a patch which is copied to x86, arm, sandbox, mikef, ag and
329 The first patch is some test things that enable your code to be compiled,
330 but that you don't want to submit because there is an existing patch for it
332 (skipping the first patch) with:
341 Let's say that patman reports an error in the second patch. Then:
349 Now you have an updated patch series. To check it:
393 Let's say one person sent comments and you get an Acked-by: on one patch.
394 Also, the patch on the list that you were waiting for has been merged,
469 not later when you can't remember which patch you changed. You can always