hgext/patchbomb.py

7996:a999dbc915f2

'''sending Mercurial changesets as a series of patch emails

The series is started off 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:

  The remainder of the changeset description.

  [Optional] The result of running diffstat on the patch.

  The patch itself, as generated by "hg export".

Each message refers to all of its predecessors using the In-Reply-To
and References headers, so they will show up as a sequence in
threaded mail and news readers, and in mail archives.

For each changeset, you will be prompted with a diffstat summary and
the changeset summary, so you can be sure you are sending the right changes.

To enable this extension:

  [extensions]
  hgext.patchbomb =

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

  [email]
  from = My Name <my@email>
  to = recipient1, recipient2, ...
  cc = cc1, cc2, ...

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
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:

  % mutt -R -f mbox

When you are previewing the patchbomb messages, you can use `formail'
(a utility that is commonly installed as part of the procmail package),
to send each message out:

  % formail -s sendmail -bm -t < mbox

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
that the patchbomb extension can automatically send patchbombs directly
from the commandline. See the [email] and [smtp] sections in hgrc(5)
for details.'''

import os, errno, socket, tempfile, cStringIO
import email.MIMEMultipart, email.MIMEBase
import email.Utils, email.Encoders, email.Generator
from mercurial import cmdutil, commands, hg, mail, patch, util

    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:

    hg email -r 3000          # send patch 3000 only
    hg email -r 3000 -r 3001  # send patches 3000 and 3001

    hg email -b               # send bundle of all patches not in default
    hg email -b DEST          # send bundle of all patches not in DEST
    hg email -b -r 3000       # bundle of all ancestors of 3000 not in default
    hg email -b -r 3000 DEST  # bundle of all ancestors of 3000 not in DEST

    Before using this command, you will need to enable email in your hgrc.
    See the [email] section in hgrc(5) for details.
    '''

    _charsets = mail._charsets(ui)

    def outgoing(dest, revs):

7997:8eb9f495e150

'''sending Mercurial changesets as a series of patch emails

The series is started off 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:

  The remainder of the changeset description.

  [Optional] The result of running diffstat on the patch.

  The patch itself, as generated by "hg export".

Each message refers to all of its predecessors using the In-Reply-To
and References headers, so they will show up as a sequence in threaded
mail and news readers, and in mail archives.

For each changeset, you will be prompted with a diffstat summary and
the changeset summary, so you can be sure you are sending the right
changes.

To enable this extension:

  [extensions]
  hgext.patchbomb =

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

  [email]
  from = My Name <my@email>
  to = recipient1, recipient2, ...
  cc = cc1, cc2, ...

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
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:

  % mutt -R -f mbox

When you are previewing the patchbomb messages, you can use `formail'
(a utility that is commonly installed as part of the procmail
package), to send each message out:

  % formail -s sendmail -bm -t < mbox

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
that the patchbomb extension can automatically send patchbombs
directly from the commandline. See the [email] and [smtp] sections in
hgrc(5) for details.'''

import os, errno, socket, tempfile, cStringIO
import email.MIMEMultipart, email.MIMEBase
import email.Utils, email.Encoders, email.Generator
from mercurial import cmdutil, commands, hg, mail, patch, util

    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:

    hg email -r 3000          # send patch 3000 only
    hg email -r 3000 -r 3001  # send patches 3000 and 3001

    hg email -b               # send bundle of all patches not in default
    hg email -b DEST          # send bundle of all patches not in DEST
    hg email -b -r 3000       # bundle of all ancestors of 3000 not in default
    hg email -b -r 3000 DEST  # bundle of all ancestors of 3000 not in DEST

    Before using this command, you will need to enable email in your
    hgrc. See the [email] section in hgrc(5) for details.
    '''

    _charsets = mail._charsets(ui)

    def outgoing(dest, revs):