Lines Matching refs:you

21 This means that you can work on a number of different branches at
24 each time. So for example if you put:
31 patches automatically (unless you use -m to disable this).
39 - Maintain a number of branches, one for each patch series you are
48 patches. Weeks later, change the patches and repeat, knowing that you
57 you need. To make this work, tell git where to find the file by typing
65 During the first run patman creates a config file for you by taking the default
85 used. Failing that you can put it into your path or ~/bin/checkpatch.pl
87 If you want to avoid sending patches to email addresses that are picked up
88 by patman but are known to bounce you can add a [bounces] section to your
100 If you want to change the defaults for patman's command-line arguments,
101 you can add a [settings] section to your .patman file.  This can be used
116 If you want to adjust settings (or aliases) that affect just a single
117 project you can add a section that looks like [project_settings] or
118 [project_alias].  If you want to use tags for your linux work, you could
141 This will create patch files in your current directory and tell you who
164 To make this script useful you must add tags like the following into any
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
180 	RFC patches, or RESEND if you are being ignored. The patch subject
189 	name here to help you keep track of multiple upstreaming efforts.
200 	Additional email addresses / aliases to send cover letter to (you
208 	Sets some notes for the patch series, which you don't want in
223 	probably a bug). If you put this tag in your patches, it will
231 	When you get this reply on the mailing list, you can add this
233 	you send out the next version. If 'Tested-by:' is set to
234 	yourself, it will be removed. No one will believe you.
247 	keep track of what happened. When you amend a commit, remember
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
304 people you can add a tag:
318 Here is an example workflow for a series of 4 patches. Let's say you have
330 but that you don't want to submit because there is an existing patch for it
331 on the list. So you can tell patman to create and check some patches
336 If you want to do all of them including the work-in-progress one, then
337 (if you are tracking an upstream branch):
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
392 Of course patches often attract comments and you need to make some updates.
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,
395 so you can drop your wip commit. So you resync with upstream:
419 Finally, you need to add a change log to the two commits you changed. You
429 When you run patman it will collect all the change logs from the different
430 commits and combine them into the cover letter, if you have one. So finally
431 you have a new series of commits:
446 1. When you change back to the us-cmd branch days or weeks later all your
448 to remember what version you are up to, who you sent the last lot of patches
451 2. If you put tags in the subject, patman will Cc the maintainers
454 3. If you want to keep the commits from each series you sent so that you can
455 compare change and see what you did, you can either create a new branch for
456 each version, or just tag the branch before you start changing it:
462 4. If you want to modify the patches a little before sending, you can do
465 5. If you want to run git send-email yourself, use the -n flag which will
468 6. It is a good idea to add the change log info as you change the commit,
469 not later when you can't remember which patch you changed. You can always
482 and make sure you are in the tools/patman directory first: