--- a/hgext/patchbomb.py Sat Apr 04 18:31:01 2009 +0200
+++ b/hgext/patchbomb.py Sat Apr 04 21:09:43 2009 +0200
@@ -37,16 +37,16 @@
as a patchbomb.
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
+the "email" command with the "-n" option (test only). You will be
prompted for an email recipient address, a subject an an introductory
-message describing the patches of your patchbomb. Then when all is
+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.
-The "-m" (mbox) option is also very useful. Instead of previewing
+The "-m" (mbox) option is also very useful. Instead of previewing
each patchbomb message in a pager or sending the messages directly,
-it will create a UNIX mailbox file with the patch emails. This
+it will create a UNIX mailbox file with the patch emails. This
mailbox file can be previewed with any mail user agent which supports
UNIX mbox files, e.g. with mutt:
@@ -173,13 +173,13 @@
'''send changesets by email
By default, diffs are sent in the format generated by hg export,
- one per message. The series starts with a "[PATCH 0 of N]"
+ one per message. The series starts with a "[PATCH 0 of N]"
introduction, which describes the series as a whole.
Each patch email has a Subject line of "[PATCH M of N] ...", using
the first line of the changeset description as the subject text.
- The message contains two or three body parts. First, the rest of
- the changeset description. Next, (optionally) if the diffstat
+ The message contains two or three body parts. First, the rest of
+ the changeset description. Next, (optionally) if the diffstat
program is installed, the result of running diffstat on the patch.
Finally, the patch itself, as generated by "hg export".