Show More
@@ -47,11 +47,11 b' as a patchbomb.' | |||
|
47 | 47 | |
|
48 | 48 | To avoid sending patches prematurely, it is a good idea to first run |
|
49 | 49 | the "email" command with the "-n" option (test only). You will be |
|
50 | prompted for an email recipient address, a subject an an introductory | |
|
50 | prompted for an email recipient address, a subject and an introductory | |
|
51 | 51 | message describing the patches of your patchbomb. Then when all is |
|
52 |
done, patchbomb messages are displayed. If PAGER environment |
|
|
53 |
is set, your pager will be fired up once for each patchbomb |
|
|
54 | so you can verify everything is alright. | |
|
52 | done, patchbomb messages are displayed. If the PAGER environment | |
|
53 | variable is set, your pager will be fired up once for each patchbomb | |
|
54 | message, so you can verify everything is alright. | |
|
55 | 55 | |
|
56 | 56 | The -m/--mbox option is also very useful. Instead of previewing each |
|
57 | 57 | patchbomb message in a pager or sending the messages directly, it will |
@@ -70,7 +70,7 b' package), to send each message out:' | |||
|
70 | 70 | That should be all. Now your patchbomb is on its way out. |
|
71 | 71 | |
|
72 | 72 | You can also either configure the method option in the email section |
|
73 |
to be a sendmail compat |
|
|
73 | to be a sendmail compatible mailer or fill out the [smtp] section so | |
|
74 | 74 | that the patchbomb extension can automatically send patchbombs |
|
75 | 75 | directly from the commandline. See the [email] and [smtp] sections in |
|
76 | 76 | hgrc(5) for details.''' |
General Comments 0
You need to be logged in to leave comments.
Login now