Lines Matching refs:to
12 - Optionally emails them out to selected people
19 It is intended to automate patch creation and make it a less
25 once, and keep the settings with each branch rather than having to
29 Series-to: fred.blogs@napier.co.nz
34 patches automatically (unless you use -m to disable this).
37 How to use this tool
44 - Add tags into the commits within each branch to indicate where the
46 normally in the top commit so it is easy to change them with 'git
50 - Check out a branch, and run this script to create and send out your
55 How to configure it
59 file 'doc/git-mailrc' in your U-Boot directory to supply the email aliases
60 you need. To make this work, tell git where to find the file by typing
66 out where to send patches pretty well.
90 If you want to avoid sending patches to email addresses that are picked up
91 by patman but are known to bounce you can add a [bounces] section to your
103 If you want to change the defaults for patman's command-line arguments,
104 you can add a [settings] section to your .patman file. This can be used
105 for any command line option by referring to the "dest" for the option in
115 smtp_server: /path/to/sendmail
121 If you want to adjust settings (or aliases) that affect just a single
123 [project_alias]. If you want to use tags for your linux work, you could
134 How to run it
147 it is thinking of sending them to. Take a look at the patch files.
151 Similar to the above, but skip the first commit and take the next 5. This
155 How to install it
158 The most up to date version of patman can be found in the U-Boot sources.
159 However to use it on other projects it may be more convenient to install it as
161 to install patman:
166 How to add tags
172 Series-to: email / alias
173 Email address / alias to send patch series to (you can add this
177 Email address / alias to Cc patch series to (you can add this
188 well. If your format.subjectprefix is set to InternalProject, then
192 Sets the name of the series. You don't need to have a name, and
193 patman does not yet use it, but it is convenient to put the branch
194 name here to help you keep track of multiple upstreaming efforts.
208 branch against patchwork to see what new reviews your series has
226 Additional email addresses / aliases to send cover letter to (you
235 the commit messages, but do want to send, The notes are joined
248 A sign-off is added automatically to your patches (this is
258 tag to the relevant commit and the script will include it when
259 you send out the next version. If 'Tested-by:' is set to
272 By adding your change lists into your commits it is easier to
274 to update the log there and then, knowing that the script will
282 useful when you want to add notes which may not make sense in the cover
290 only appear in the cover-letter changelog. This is useful to summarize
291 changes made with Commit-changes, or to add additional context to
295 This copies a single patch to another email address. Note that the
300 This tells patman to sort and/or uniq the change logs. Changes may be
308 Use 'sort' to sort the entries, and 'uniq' to include only
313 This tag is stripped out but is used to generate the Message-Id
328 Exercise for the reader: Try adding some tags to one of your current
336 whole series is sent to the recipients in Series-to: and Series-cc.
337 You can Cc individual patches to other people with the Patch-cc: tag. Tags
338 in the subject are also picked up to Cc patches. For example, a commit like
348 This should make sending out e-mails to the right people easier.
354 will create a patch which is copied to x86, arm, sandbox, mikef, ag and
357 If you have a cover letter it will get sent to the union of the Patch-cc
358 lists of all of the other patches. If you want to sent it to additional
370 Patman has a very basic integration with Patchwork. If you point patman to
374 To set this up, add a Series-link tag to one of the commits in your series
385 21 x86: mtrr: Update the command to use the new mtrr
409 which should show that there are no new responses compared to this new branch.
411 There is also a -C option to list the comments received for each patch.
417 The basic workflow is to create your commits, add some tags to the top
418 commit, and type 'patman' to check and send them.
422 your tree where 'us' means your upstreaming activity (newest to oldest as
428 0c859a9 Rename run_command2() to run_command()
429 a74443f sandbox: Rename run_command() to builtin_run_command()
431 The first patch is some test things that enable your code to be compiled,
432 but that you don't want to submit because there is an existing patch for it
433 on the list. So you can tell patman to create and check some patches
438 If you want to do all of them including the work-in-progress one, then
446 <change 'pick' to 'edit' in 89234f5>
447 <use editor to make code changes>
455 Let's say it is now clean and you want to send it. Now you need to set up
460 Use your editor to add some tags, so that the whole commit message is:
464 in case the hush parser is bring used, so rename this function to
467 Series-to: u-boot
473 At present two parsers have similar code to execute commands. Also
481 You want this to be an RFC and Cc the whole series to the bfin alias and
482 to Marek. Two of the patches have tags (those are the bits at the front of
483 the subject that say mmc: sparc: and sandbox:), so 8d640a7 will be Cc'd to
484 mmc and sparc, and the last one to sandbox.
486 Now to send the patches, take off the -n flag:
494 Of course patches often attract comments and you need to make some updates.
501 Add this to a tag in your top commit:
505 You can use then patman to collect the Acked-by tag to the correct commit,
520 and use git rebase -i to edit the commits, dropping the wip one.
522 Then update the Series-cc: in the top commit to add the person who reviewed
531 Series-to: u-boot
537 Finally, you need to add a change log to the two commits you changed. You
538 add change logs to each individual commit where the changes happened, like
542 - Updated the command decoder to reduce code size
553 cfbe330 Rename run_command2() to run_command()
554 0682677 sandbox: Rename run_command() to builtin_run_command()
556 so to send them:
566 1. When you change back to the us-cmd branch days or weeks later all your
568 to remember what version you are up to, who you sent the last lot of patches
569 to, or anything about the change logs.
574 3. If you want to keep the commits from each series you sent so that you can
582 4. If you want to modify the patches a little before sending, you can do
585 5. If you want to run git send-email yourself, use the -n flag which will
588 6. It is a good idea to add the change log info as you change the commit,
592 7. Some mailing lists have size limits and when we add binary contents to
593 our patches it's easy to exceed the size limits. Use "--no-binary" to
594 generate patches without any binary contents. You are supposed to include
595 a link to a git repository in your "Commit-notes", "Series-notes" or
596 "Cover-letter" for maintainers to fetch the original commit.
626 It would be nice if this could handle the In-reply-to side of things.
628 The tests are incomplete, as is customary. Use the 'test' subcommand to run