comparison hgext/patchbomb.py @ 8076:5ec526c1a32f

help texts: write command line switches as -a/--abc

8075:1f0a5a5fff43

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 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
files, e.g. with mutt:

    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".

    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 --bundle, changesets are selected as for --outgoing, but a
    single email containing a binary Mercurial bundle as an attachment
    will be sent.

    Examples:

           _('send changes not in target as a binary bundle')),
          ('', 'bundlename', 'bundle',
           _('file name of the bundle attachment')),
          ('r', 'rev', [], _('a revision to send')),
          ('', 'force', None,
           _('run even when remote repository is unrelated (with -b)')),
          ('', 'base', [],
           _('a base changeset to specify instead of a destination (with -b)')),
          ('', 'intro', None,
           _('send an introduction email for a single patch')),
         ] + emailopts + commands.remoteopts,
         _('hg email [OPTION]... [DEST]...'))
}

8076:5ec526c1a32f

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 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
files, e.g. with mutt:

    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".

    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 -b/--bundle, changesets are selected as for --outgoing, but a
    single email containing a binary Mercurial bundle as an attachment
    will be sent.

    Examples:

           _('send changes not in target as a binary bundle')),
          ('', 'bundlename', 'bundle',
           _('file name of the bundle attachment')),
          ('r', 'rev', [], _('a revision to send')),
          ('', 'force', None,
           _('run even when remote repository is unrelated '
             '(with -b/--bundle)')),
          ('', 'base', [],
           _('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,
         _('hg email [OPTION]... [DEST]...'))
}