Lines Matching full:patches

11 - Runs the patches through checkpatch.pl and its own checks
29 patches automatically (unless you use -m to disable this).
46 patches. Weeks later, change the patches and repeat, knowing that you
61 out where to send patches pretty well.
85 If you want to avoid sending patches to email addresses that are picked up
135 If it can't detect the upstream branch, try telling it how many patches
179 	RFC patches, or RESEND if you are being ignored. The patch subject
221 	A sign-off is added automatically to your patches (this is
222 	probably a bug). If you put this tag in your patches, it will
273 patch series and see how the patches turn out.
276 Where Patches Are Sent
279 Once the patches are created, patman sends them using git send-email. The
281 You can Cc individual patches to other people with the Patch-cc: tag. Tags
282 in the subject are also picked up to Cc patches. For example, a commit like
302 lists of all of the other patches. If you want to sent it to additional
308 list for any of the patches.
317 Here is an example workflow for a series of 4 patches. Let's say you have
318 these rather contrived patches in the following order in branch us-cmd in
330 on the list. So you can tell patman to create and check some patches
379 to Marek. Two of the patches have tags (those are the bits at the front of
383 Now to send the patches, take off the -n flag:
387 The patches will be created, shown in your editor, and then sent along with
391 Of course patches often attract comments and you need to make some updates.
447 to remember what version you are up to, who you sent the last lot of patches
461 4. If you want to modify the patches a little before sending, you can do