Lines Matching refs:patch
9 Patman patch manager
14 - Creates patch directly from your branch
26 It is intended to automate patch creation and make it a less
33 git format-patch, git send-email, etc. with the correct parameters
49 pip install patch-manager
61 - Maintain a number of branches, one for each patch series you are
98 contract is that the script should accept a patch file name and return
173 This will create patch files in your current directory and tell you who
174 it is thinking of sending them to. Take a look at the patch files:
204 Email address / alias to send patch series to (you can add this
208 Email address / alias to Cc patch series to (you can add this
212 Sets the version number of this patch series
216 RFC patches, or RESEND if you are being ignored. The patch subject
220 the patch shows like: [InternalProject][RFC/RESEND PATCH]
224 tree such as net or net-next if that needs to be specified. The patch
235 URL you want is the one for the series itself, not any particular patch.
260 This is the patch set title
270 Sets some notes for the patch series, which you don't want in
282 Similar, but for a single commit (patch). These notes will appear
283 immediately below the --- cut in the patch file::
297 These indicate that someone has tested/reviewed/acked your patch.
354 This copies a single patch to another email address. Note that the
377 (but logically the same patch) as other patches that have been
390 patch series and see how the patches turn out.
413 will create a patch which is copied to x86, arm, sandbox, mikef, ag and
442 and patman will show you each patch and what review tags have been collected,
454 This shows that patch 21 and 22 were sent out with one review but have since
476 There is also a -C option to list the comments received for each patch.
496 The first patch is some test things that enable your code to be compiled,
497 but that you don't want to submit because there is an existing patch for it
499 (skipping the first patch) with:
512 Let's say that patman reports an error in the second patch. Then:
522 Now you have an updated patch series. To check it:
572 Let's say one person sent comments and you get an Acked-by: on one patch.
573 Also, the patch on the list that you were waiting for has been merged,
672 not later when you can't remember which patch you changed. You can always
680 change. For clarity, if there are no changes for this patch in the most
681 recent revision of the series, a note will be added. For example, a patch