14 first line of the changeset description as the subject text. The |
14 first line of the changeset description as the subject text. The |
15 message contains two or three body parts: |
15 message contains two or three body parts: |
16 |
16 |
17 - The changeset description. |
17 - The changeset description. |
18 - [Optional] The result of running diffstat on the patch. |
18 - [Optional] The result of running diffstat on the patch. |
19 - The patch itself, as generated by "hg export". |
19 - The patch itself, as generated by :hg:`export`. |
20 |
20 |
21 Each message refers to the first in the series using the In-Reply-To |
21 Each message refers to the first in the series using the In-Reply-To |
22 and References headers, so they will show up as a sequence in threaded |
22 and References headers, so they will show up as a sequence in threaded |
23 mail and news readers, and in mail archives. |
23 mail and news readers, and in mail archives. |
24 |
24 |
36 bcc = bcc1, bcc2, ... |
36 bcc = bcc1, bcc2, ... |
37 |
37 |
38 Use ``[patchbomb]`` as configuration section name if you need to |
38 Use ``[patchbomb]`` as configuration section name if you need to |
39 override global ``[email]`` address settings. |
39 override global ``[email]`` address settings. |
40 |
40 |
41 Then you can use the "hg email" command to mail a series of changesets |
41 Then you can use the :hg:`email` command to mail a series of |
42 as a patchbomb. |
42 changesets as a patchbomb. |
43 |
43 |
44 To avoid sending patches prematurely, it is a good idea to first run |
44 To avoid sending patches prematurely, it is a good idea to first run |
45 the "email" command with the "-n" option (test only). You will be |
45 the :hg:`email` command with the "-n" option (test only). You will be |
46 prompted for an email recipient address, a subject and an introductory |
46 prompted for an email recipient address, a subject and an introductory |
47 message describing the patches of your patchbomb. Then when all is |
47 message describing the patches of your patchbomb. Then when all is |
48 done, patchbomb messages are displayed. If the PAGER environment |
48 done, patchbomb messages are displayed. If the PAGER environment |
49 variable is set, your pager will be fired up once for each patchbomb |
49 variable is set, your pager will be fired up once for each patchbomb |
50 message, so you can verify everything is alright. |
50 message, so you can verify everything is alright. |
194 the first line of the changeset description as the subject text. |
194 the first line of the changeset description as the subject text. |
195 The message contains two or three parts. First, the changeset |
195 The message contains two or three parts. First, the changeset |
196 description. Next, (optionally) if the diffstat program is |
196 description. Next, (optionally) if the diffstat program is |
197 installed and -d/--diffstat is used, the result of running |
197 installed and -d/--diffstat is used, the result of running |
198 diffstat on the patch. Finally, the patch itself, as generated by |
198 diffstat on the patch. Finally, the patch itself, as generated by |
199 "hg export". |
199 :hg:`export`. |
200 |
200 |
201 By default the patch is included as text in the email body for |
201 By default the patch is included as text in the email body for |
202 easy reviewing. Using the -a/--attach option will instead create |
202 easy reviewing. Using the -a/--attach option will instead create |
203 an attachment for the patch. With -i/--inline an inline attachment |
203 an attachment for the patch. With -i/--inline an inline attachment |
204 will be created. |
204 will be created. |