Lines Matching refs:it

16 It is intended to automate patch creation and make it a less
18 since it uses the checkpatch.pl script.
20 It is configured almost entirely by tags it finds in your commits.
43 normally in the top commit so it is easy to change them with 'git
46 automatically determine the number of commits in it (optional)
52 How to configure it
85 used. Failing that you can put it into your path or ~/bin/checkpatch.pl
129 How to run it
136 If it can't detect the upstream branch, try telling it how many patches
142 it is thinking of sending them to. Take a look at the patch files.
150 How to install it
154 However to use it on other projects it may be more convenient to install it as
179 	Sets the subject prefix. Normally empty but it can be RFC for
188 	patman does not yet use it, but it is convenient to put the branch
223 	probably a bug). If you put this tag in your patches, it will
232 	tag to the relevant commit and the script will include it when
234 	yourself, it will be removed. No one will believe you.
246 	By adding your change lists into your commits it is easier to
254 	interpreted by git send-email if you use it.
302 If you have a cover letter it will get sent to the union of the Patch-cc
303 lists of all of the other patches. If you want to sent it to additional
330 but that you don't want to submit because there is an existing patch for it
349 Now you have an updated patch series. To check it:
353 Let's say it is now clean and you want to send it. Now you need to set up
409 and remove the Series-prefix: tag since it it isn't an RFC any more. The
429 When you run patman it will collect all the change logs from the different
442 and it will create and send the version 2 series.
456 each version, or just tag the branch before you start changing it: