Show More
@@ -23,13 +23,10 b'' | |||||
23 | # the changeset summary, so you can be sure you are sending the right |
|
23 | # the changeset summary, so you can be sure you are sending the right | |
24 | # changes. |
|
24 | # changes. | |
25 | # |
|
25 | # | |
26 | # It is best to run this script with the "-n" (test only) flag before |
|
26 | # To enable this extension: | |
27 | # firing it up "for real", in which case it will use your pager to |
|
|||
28 | # display each of the messages that it would send. |
|
|||
29 | # |
|
27 | # | |
30 | # The "-m" (mbox) option will create an mbox file instead of sending |
|
28 | # [extensions] | |
31 | # the messages directly. This can be reviewed e.g. with "mutt -R -f mbox", |
|
29 | # hgext.patchbomb = | |
32 | # and finally sent with "formail -s sendmail -bm -t < mbox". |
|
|||
33 | # |
|
30 | # | |
34 | # To configure other defaults, add a section like this to your hgrc |
|
31 | # To configure other defaults, add a section like this to your hgrc | |
35 | # file: |
|
32 | # file: | |
@@ -39,6 +36,32 b'' | |||||
39 | # to = recipient1, recipient2, ... |
|
36 | # to = recipient1, recipient2, ... | |
40 | # cc = cc1, cc2, ... |
|
37 | # cc = cc1, cc2, ... | |
41 | # bcc = bcc1, bcc2, ... |
|
38 | # bcc = bcc1, bcc2, ... | |
|
39 | # | |||
|
40 | # Then you can use the "hg email" command to mail a series of changesets | |||
|
41 | # as a patchbomb. | |||
|
42 | # | |||
|
43 | # To avoid sending patches prematurely, it is a good idea to first run | |||
|
44 | # the "email" command with the "-n" option (test only). You will be | |||
|
45 | # prompted for an email recipient address, a subject an an introductory | |||
|
46 | # message describing the patches of your patchbomb. Then when all is | |||
|
47 | # done, your pager will be fired up once for each patchbomb message, so | |||
|
48 | # you can verify everything is alright. | |||
|
49 | # | |||
|
50 | # The "-m" (mbox) option is also very useful. Instead of previewing | |||
|
51 | # each patchbomb message in a pager or sending the messages directly, | |||
|
52 | # it will create a UNIX mailbox file with the patch emails. This | |||
|
53 | # mailbox file can be previewed with any mail user agent which supports | |||
|
54 | # UNIX mbox files, i.e. with mutt: | |||
|
55 | # | |||
|
56 | # % mutt -R -f mbox | |||
|
57 | # | |||
|
58 | # When you are previewing the patchbomb messages, you can use `formail' | |||
|
59 | # (a utility that is commonly installed as part of the procmail package), | |||
|
60 | # to send each message out: | |||
|
61 | # | |||
|
62 | # % formail -s sendmail -bm -t < mbox | |||
|
63 | # | |||
|
64 | # That should be all. Now your patchbomb is on its way out. | |||
42 |
|
65 | |||
43 | from mercurial.demandload import * |
|
66 | from mercurial.demandload import * | |
44 | demandload(globals(), '''email.MIMEMultipart email.MIMEText email.Utils |
|
67 | demandload(globals(), '''email.MIMEMultipart email.MIMEText email.Utils |
General Comments 0
You need to be logged in to leave comments.
Login now