--- a/hgext/patchbomb.py Sat Apr 18 00:21:11 2009 -0700
+++ b/hgext/patchbomb.py Sat Apr 18 14:40:21 2009 +0200
@@ -46,7 +46,7 @@
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
+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 mailbox file
can be previewed with any mail user agent which supports UNIX mbox
@@ -185,11 +185,11 @@
program is installed, the result of running diffstat on the patch.
Finally, the patch itself, as generated by "hg export".
- With --outgoing, emails will be generated for patches not found in
- the destination repository (or only those which are ancestors of
- the specified revisions if any are provided)
+ With -o/--outgoing, emails will be generated for patches not found
+ in the destination repository (or only those which are ancestors
+ of the specified revisions if any are provided)
- With --bundle, changesets are selected as for --outgoing, but a
+ With -b/--bundle, changesets are selected as for --outgoing, but a
single email containing a binary Mercurial bundle as an attachment
will be sent.
@@ -477,9 +477,11 @@
_('file name of the bundle attachment')),
('r', 'rev', [], _('a revision to send')),
('', 'force', None,
- _('run even when remote repository is unrelated (with -b)')),
+ _('run even when remote repository is unrelated '
+ '(with -b/--bundle)')),
('', 'base', [],
- _('a base changeset to specify instead of a destination (with -b)')),
+ _('a base changeset to specify instead of a destination '
+ '(with -b/--bundle)')),
('', 'intro', None,
_('send an introduction email for a single patch')),
] + emailopts + commands.remoteopts,