Mercurial > hg
changeset 8512:b87e5ad94229
patchbomb: minor typo and language fixes
| author | Cédric Duval <cedricduval@free.fr> |
|---|---|
| date | Tue, 19 May 2009 00:06:19 +0200 |
| parents | 32ff5ba0d312 |
| children | b9308af35ba2 |
| files | hgext/patchbomb.py |
| diffstat | 1 files changed, 5 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/hgext/patchbomb.py Tue May 19 00:02:54 2009 +0200 +++ b/hgext/patchbomb.py Tue May 19 00:06:19 2009 +0200 @@ -47,11 +47,11 @@ To avoid sending patches prematurely, it is a good idea to first run the "email" command with the "-n" option (test only). You will be -prompted for an email recipient address, a subject an an introductory +prompted for an email recipient address, a subject and an introductory message describing the patches of your patchbomb. Then when all is -done, patchbomb messages are displayed. If PAGER environment variable -is set, your pager will be fired up once for each patchbomb message, -so you can verify everything is alright. +done, patchbomb messages are displayed. If the PAGER environment +variable is set, your pager will be fired up once for each patchbomb +message, so you can verify everything is alright. The -m/--mbox option is also very useful. Instead of previewing each patchbomb message in a pager or sending the messages directly, it will @@ -70,7 +70,7 @@ That should be all. Now your patchbomb is on its way out. You can also either configure the method option in the email section -to be a sendmail compatable mailer or fill out the [smtp] section so +to be a sendmail compatible mailer or fill out the [smtp] section so that the patchbomb extension can automatically send patchbombs directly from the commandline. See the [email] and [smtp] sections in hgrc(5) for details.'''