Lines Matching refs:to
14 - Optionally emails them out to selected people
16 It is intended to automate patch creation and make it a less
22 once, and keep the settings with each branch rather than having to
26 Series-to: fred.blogs@napier.co.nz
31 patches automatically (unless you use -m to disable this).
34 How to use this tool
41 - Add tags into the commits within each branch to indicate where the
43 normally in the top commit so it is easy to change them with 'git
47 - Check out a branch, and run this script to create and send out your
52 How to configure it
56 file 'doc/git-mailrc' in your U-Boot directory to supply the email aliases
57 you need. To make this work, tell git where to find the file by typing
63 out where to send patches pretty well.
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
102 for any command line option by referring to the "dest" for the option in
116 If you want to adjust settings (or aliases) that affect just a single
118 [project_alias]. If you want to use tags for your linux work, you could
129 How to run it
142 it is thinking of sending them to. Take a look at the patch files.
146 Similar to the above, but skip the first commit and take the next 5. This
150 How to install it
153 The most up to date version of patman can be found in the U-Boot sources.
154 However to use it on other projects it may be more convenient to install it as
156 to install patman:
161 How to add tags
167 Series-to: email / alias
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
183 well. If your format.subjectprefix is set to InternalProject, then
187 Sets the name of the series. You don't need to have a name, and
188 patman does not yet use it, but it is convenient to put the branch
189 name here to help you keep track of multiple upstreaming efforts.
200 Additional email addresses / aliases to send cover letter to (you
209 the commit messages, but do want to send, The notes are joined
222 A sign-off is added automatically to your patches (this is
232 tag to the relevant commit and the script will include it when
233 you send out the next version. If 'Tested-by:' is set to
246 By adding your change lists into your commits it is easier to
248 to update the log there and then, knowing that the script will
252 This copies a single patch to another email address. Note that the
257 This tells patman to sort and/or uniq the change logs. It is
259 Use 'sort' to sort the entries, and 'uniq' to include only
273 Exercise for the reader: Try adding some tags to one of your current
281 whole series is sent to the recipients in Series-to: and Series-cc.
282 You can Cc individual patches to other people with the Patch-cc: tag. Tags
283 in the subject are also picked up to Cc patches. For example, a commit like
293 This should make sending out e-mails to the right people easier.
299 will create a patch which is copied to x86, arm, sandbox, mikef, ag and
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
315 The basic workflow is to create your commits, add some tags to the top
316 commit, and type 'patman' to check and send them.
320 your tree where 'us' means your upstreaming activity (newest to oldest as
326 0c859a9 Rename run_command2() to run_command()
327 a74443f sandbox: Rename run_command() to builtin_run_command()
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
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
344 <change 'pick' to 'edit' in 89234f5>
345 <use editor to make code changes>
353 Let's say it is now clean and you want to send it. Now you need to set up
358 Use your editor to add some tags, so that the whole commit message is:
362 in case the hush parser is bring used, so rename this function to
365 Series-to: u-boot
371 At present two parsers have similar code to execute commands. Also
379 You want this to be an RFC and Cc the whole series to the bfin alias and
380 to Marek. Two of the patches have tags (those are the bits at the front of
381 the subject that say mmc: sparc: and sandbox:), so 8d640a7 will be Cc'd to
382 mmc and sparc, and the last one to sandbox.
384 Now to send the patches, take off the -n flag:
392 Of course patches often attract comments and you need to make some updates.
400 and use git rebase -i to edit the commits, dropping the wip one. You add
401 the ack tag to one commit:
413 Series-to: u-boot
419 Finally, you need to add a change log to the two commits you changed. You
420 add change logs to each individual commit where the changes happened, like
424 - Updated the command decoder to reduce code size
435 cfbe330 Rename run_command2() to run_command()
436 0682677 sandbox: Rename run_command() to builtin_run_command()
438 so to send them:
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
449 to, or anything about the change logs.
454 3. If you want to keep the commits from each series you sent so that you can
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,
479 It would be nice if this could handle the In-reply-to side of things.
481 The tests are incomplete, as is customary. Use the --test flag to run them,
484 $ cd /path/to/u-boot