13 Each patch email has a Subject line of "[PATCH M of N] ...", using the

    13 Each patch email has a Subject line of "[PATCH M of N] ...", using the first

    14 first line of the changeset description as the subject text. The

    14 line of the changeset description as the subject text. The message contains

    15 message contains two or three body parts:

    15 two or three body parts:

    23 Each message refers to the first in the series using the In-Reply-To

    23 Each message refers to the first in the series using the In-Reply-To and

    24 and References headers, so they will show up as a sequence in threaded

    24 References headers, so they will show up as a sequence in threaded mail and

    25 mail and news readers, and in mail archives.

    25 news readers, and in mail archives.

    26 

    26 

    27 With the -d/--diffstat option, you will be prompted for each changeset

    27 With the -d/--diffstat option, you will be prompted for each changeset with a

    28 with a diffstat summary and the changeset summary, so you can be sure

    28 diffstat summary and the changeset summary, so you can be sure you are sending

    29 you are sending the right changes.

    29 the right changes.

    30 

    30 

    31 To configure other defaults, add a section like this to your hgrc

    31 To configure other defaults, add a section like this to your hgrc file:

    32 file:

    40 Then you can use the "hg email" command to mail a series of changesets

    39 Then you can use the "hg email" command to mail a series of changesets as a

    41 as a patchbomb.

    40 patchbomb.

    42 

    41 

    43 To avoid sending patches prematurely, it is a good idea to first run

    42 To avoid sending patches prematurely, it is a good idea to first run the

    44 the "email" command with the "-n" option (test only). You will be

    43 "email" command with the "-n" option (test only). You will be prompted for an

    45 prompted for an email recipient address, a subject and an introductory

    44 email recipient address, a subject and an introductory message describing the

    46 message describing the patches of your patchbomb. Then when all is

    45 patches of your patchbomb. Then when all is done, patchbomb messages are

    47 done, patchbomb messages are displayed. If the PAGER environment

    46 displayed. If the PAGER environment variable is set, your pager will be fired

    48 variable is set, your pager will be fired up once for each patchbomb

    47 up once for each patchbomb message, so you can verify everything is alright.

    49 message, so you can verify everything is alright.

    48 

    50 

    49 The -m/--mbox option is also very useful. Instead of previewing each patchbomb

    51 The -m/--mbox option is also very useful. Instead of previewing each

    50 message in a pager or sending the messages directly, it will create a UNIX

    52 patchbomb message in a pager or sending the messages directly, it will

    51 mailbox file with the patch emails. This mailbox file can be previewed with

    53 create a UNIX mailbox file with the patch emails. This mailbox file

    52 any mail user agent which supports UNIX mbox files, e.g. with mutt:

    54 can be previewed with any mail user agent which supports UNIX mbox

    55 files, e.g. with mutt:

    59 When you are previewing the patchbomb messages, you can use `formail'

    56 When you are previewing the patchbomb messages, you can use `formail' (a

    60 (a utility that is commonly installed as part of the procmail

    57 utility that is commonly installed as part of the procmail package), to send

    61 package), to send each message out:

    58 each message out:

    67 You can also either configure the method option in the email section

    64 You can also either configure the method option in the email section to be a

    68 to be a sendmail compatible mailer or fill out the [smtp] section so

    65 sendmail compatible mailer or fill out the [smtp] section so that the

    69 that the patchbomb extension can automatically send patchbombs

    66 patchbomb extension can automatically send patchbombs directly from the

    70 directly from the commandline. See the [email] and [smtp] sections in

    67 commandline. See the [email] and [smtp] sections in hgrc(5) for details.

    71 hgrc(5) for details.'''

    68 '''

   179     By default, diffs are sent in the format generated by hg export,

   176     By default, diffs are sent in the format generated by hg export, one per

   180     one per message. The series starts with a "[PATCH 0 of N]"

   177     message. The series starts with a "[PATCH 0 of N]" introduction, which

   181     introduction, which describes the series as a whole.

   178     describes the series as a whole.

   182 

   179 

   183     Each patch email has a Subject line of "[PATCH M of N] ...", using

   180     Each patch email has a Subject line of "[PATCH M of N] ...", using the

   184     the first line of the changeset description as the subject text.

   181     first line of the changeset description as the subject text. The message

   185     The message contains two or three parts. First, the changeset

   182     contains two or three parts. First, the changeset description. Next,

   186     description. Next, (optionally) if the diffstat program is

   183     (optionally) if the diffstat program is installed and -d/--diffstat is

   187     installed and -d/--diffstat is used, the result of running

   184     used, the result of running diffstat on the patch. Finally, the patch

   188     diffstat on the patch. Finally, the patch itself, as generated by

   185     itself, as generated by "hg export".

   189     "hg export".

   186 

   190 

   187     By default the patch is included as text in the email body for easy

   191     By default the patch is included as text in the email body for

   188     reviewing. Using the -a/--attach option will instead create an attachment

   192     easy reviewing. Using the -a/--attach option will instead create

   189     for the patch. With -i/--inline an inline attachment will be created.

   193     an attachment for the patch. With -i/--inline an inline attachment

   190 

   194     will be created.

   191     With -o/--outgoing, emails will be generated for patches not found in the

   195 

   192     destination repository (or only those which are ancestors of the specified

   196     With -o/--outgoing, emails will be generated for patches not found

   193     revisions if any are provided)

   197     in the destination repository (or only those which are ancestors

   194 

   198     of the specified revisions if any are provided)

   195     With -b/--bundle, changesets are selected as for --outgoing, but a single

   199 

   196     email containing a binary Mercurial bundle as an attachment will be sent.

   200     With -b/--bundle, changesets are selected as for --outgoing, but a

   201     single email containing a binary Mercurial bundle as an attachment

   202     will be sent.

   221     Before using this command, you will need to enable email in your

   215     Before using this command, you will need to enable email in your hgrc. See

   222     hgrc. See the [email] section in hgrc(5) for details.

   216     the [email] section in hgrc(5) for details.