�
1�3\c@@s�dZd
dl
mZ
d
dljZd
dljZd
dl	j
jZd
dl
j
jZd
dljZd
dlZd
dlZd
dlZd
dlmZ
d
dlmZmZmZmZmZmZmZm Z!m"Z"m#Z#m$Z$m%Z%m&Z&m'Z'
d
dl(m)Z)
e'j*Z*iZ+e$j,e+�
Z,iZ-e$j.e-�
Z.e.ddd	e/�

e.dd
d	e/�

e.ddd	e/�

e.ddd	e0�

e.dd
d	e/�

e.ddd	e/�

e.ddd	d�

e.ddd	e/�

e.ddd	e/�

e.ddd	e/�

e#j1rej2Z3n	ej4Z3dZ5d�Z6d�Z7d�Z8e/dd�Z9d�Z:d�Z;d�Z<e/d�
Z=d�Z>d�Z?d �Z@d!�ZAd"�ZBe/d#�
ZCd$�ZDd%�ZEd&d'e/ed(�
fd)d*e/ed+�
fd,d-e/ed.�
fd&d
ged/�
ed0�
fd1dged2�
ed0�
fd&de/ed3�
fd4d5e/ed6�
fd&d7d&ed8�
ed9�
fd&d:d&ed;�
ed<�
fd=dd&ed>�
ed0�
fd?d@e/edA�
fdBdCd&edD�
ed<�
fd&dgedE�
ed0�
fdFdGd&edH�
edI�
fd&dJd&edK�
edL�
fd&dMgedN�
edO�
fdPdgedQ�
ed0�
fgZFe,dRdSdTe/edU�
fd&dVe/edW�
fdXdYe/edZ�
fd[d\e/ed]�
fd^d_d&ed`�
eda�
fd&dbd\edc�
edd�
fdedfgedg�
edh�
fd&die/edj�
fd&dkgedl�
edh�
fd&de/edm�
fg
eFejGedn�
doe,jH�
dp��
ZIdS(qss	command to send 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 changeset description.
- [Optional] The result of running diffstat on the patch.
- The patch itself, as generated by :hg:`export`.

Each message refers to the first in the series 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.

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

  [email]
  from = My Name <my@email>
  to = recipient1, recipient2, ...
  cc = cc1, cc2, ...
  bcc = bcc1, bcc2, ...
  reply-to = address1, address2, ...

Use ``[patchbomb]`` as configuration section name if you need to
override global ``[email]`` address settings.

Then you can use the :hg:`email` command to mail a series of
changesets as a patchbomb.

You can also either configure the method option in the email section
to be a sendmail compatible 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.

By default, :hg:`email` will prompt for a ``To`` or ``CC`` header if
you do not supply one via configuration or the command line.  You can
override this to never prompt by configuring an empty value::

  [email]
  cc =

You can control the default inclusion of an introduction message with the
``patchbomb.intro`` configuration option. The configuration is always
overwritten by command line flags like --intro and --desc::

  [patchbomb]
  intro=auto   # include introduction message if more than 1 patch (default)
  intro=never  # never include an introduction message
  intro=always # always include an introduction message

You can specify a template for flags to be added in subject prefixes. Flags
specified by --flag option are exported as ``{flags}`` keyword::

  [patchbomb]
  flagtemplate = "{separate(' ',
                            ifeq(branch, 'default', '', branch|upper),
                            flags)}"

You can set patchbomb to always ask for confirmation by setting
``patchbomb.confirm`` to true.
i(
tabsolute_importN(
t
_(tcmdutiltcommandstencodingterrort	formatterthgtmailtnodetpatchtpycompatt	registrartscmutilt	templatertutil(
tdateutilt	patchbombt
bundletypetdefaulttbcctcctconfirmtflagtemplatetfromtintrotautot	publicurlsreply-tottosships-with-hg-corecC@s<|
j�}|j
jd
d�}|r8d|||
fSdS(sKAdd a header pointing to a public URL where the changeset is available
    RRs/Available At %s
#              hg pull %s -r %sN(trepotuitconfigtNone(tseqtctxRR((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt_addpullheader�s



c

C@s!tj
jd
�

ttjd
<dS(Ntpullurl(RtextraexporttappendR#textraexportmap(
R((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pytuisetup�s

cC@s$|
j�sdS|
j
jd
�

dS(Nslast-email.txt(tlocalt_wlockfreeprefixtadd(RR((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt	reposetup�s


t
:cC@s+|r|
d
|7}
n|j|
||�S(Ns [%s](
tprompt(RR.Rtrest((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyR.�s


cC@s�|jd
d�}|
j
d�
s0|
j
d�
r9t}n{|dkrNt}nf|dkrct}nQ|dkr~|dk}n6|jtd�
|�

|jtd	�
�

|dk}|S(
s-is an introductory message apparently wanted?RRtdesctalwaystneverRi
s,warning: invalid patchbomb.intro value "%s"
s'(should be one of always, never, auto)
(RtgettTruetFalset	write_errR
(RtoptstnumbertintroconfigR((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pytintrowanted�s

	

	

	





cC@s�|jd
d�}|s%dj
|�
Stj�}i
tj|�
d6}tj||d|��G}|j�
|j	d|
|�

|j
dd|j|d	d
�

�
WdQX|j�S(s(build flag string optionally by templateRRt
 ttemplatet
patchbombflagR"tflagss%stnametflagN(
RtjoinRtstringioRt
unquotestringRttemplateformattert	startitemtcontexttwritet
formatlisttgetvalue(RRtrevR>ttmpltoutR7tfm((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt_formatflags�s









(
c	C@s^t||
||�}|r(d
|}n|s6d|St
d|�
}d||||fSdS(sbuild prefix to patch subjectR;s	[PATCH%s]s%ds[PATCH %0*d of %d%s]N(RNtlen(	RRRJR>tidxttotaltnumberedR@ttlen((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt
_formatprefix�s




c
C@sAg}
d}d
}xt|D]l}
|
j
d�
rV|
j
d�
r|
j�d}qqn|
j
d�
st|
j
d�
rxPn|
j|
�

qW|	r�|r�t�
n|jd�
r�|jd�
r�d	j|
d
�
j�p�d}|d7}n|jd
�
rk
x*|r&
|dj
d�
r&
|jd�

q�W|r=
|jd�

nx+|rg
|dj�rg
|jd�

q@
Wnt	j
|�
}|jd�
r�
||d7}n|jd�
p�
|jd�
}|s�
|jd�
r�
|d	j|�
7}n|rItj�}|r'|j
tj||||jd�
��

ntjd	j|�
d|jd�
�}tj|�
}|	sg|
j|�
D]*}|jd�
s�|jd�
rs|^qs}|r�|d}	q|d
kr�tj|
|dd|d|�}	qtj|
|d�}	nd}|jd�
rd}n|dtj|	�
|d<|j
|�

ntj|d|jd�
�

}t||
||jd�
|||�}|
dj�jd �
}|s�d!j||jd"�
p�|g�
}nd!j||g�
}tj||||jd�
�|d#<||d$<d%||d&<d%||d'<|||fS((Ntt
#s	# Node IDi����sdiff -rs
diff --gittattachtbodys

i
s"Patch subject is complete summary.s


tplainis# tdiffstats

tinlinettestsx-patchs.patchs.diffs%b-%n.patchtseqnoRQs%b.patcht
attachments; filename=sContent-DispositiontdisplayR@s. R;tsubjecttSubjectsX-Mercurial-Nodes%isX-Mercurial-Series-IndexsX-Mercurial-Series-Total(R t
startswithtsplitR&t
ValueErrorR3RAtstriptpopR
RZtemimemultipartt
MIMEMultipartRWRt
mimeencodet
mimetextpatchtnodemodtbintnodetagstendswithRtmakefilenameRtstrfromlocalRTtrstript
headencode(RRRJt
patchlinesR7t	_charsetsRPRQRRt	patchnameR0R	RXtlinetdst
addattachmenttmsgt
ptbinnodet
tt	patchtagstdispositiontprefixtsubj((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt	makepatch�s~










	
















+




*








	

	


'
%




ck@s�|j}|d
j
�}x�|
D]�}||krh|dj�sR|dj�rh|jtd�
�

nt�}tj	||g
|dt
j||dt�
�

|j
�jd�
V
q WdS(slreturn a list of patches for a list of revisions

    Each patch in the list is itself a list of lines.
    t
.s3warning: working directory has uncommitted changes
R7tgits

N(RRJR tfilestdeletedtwarnR
RBRt
exportfileR
tdifffeatureoptsR4RIRc(RtrevsR7Rtprevt
rtoutput((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt_getpatches/
s	



,
	


cK@s�|j}t
jd
d�
}tjj|d�}|jdd�}|rU||d<nz*tj||||
|�
t	j
|�
SWdytj|�

Wntk
r�


n
Xtj
|�

XdS(s�return a bundle containing changesets missing in "dest"

    The `opts` keyword-arguments are the same as the one accepted by the
    `bundle` command.

    The bundle is a returned as a single in-memory binary blob.
    Rshg-email-bundle-tbundleRRttypeN(RRtmkdtemptostpathRARRR�RtreadfiletunlinktOSErrortrmdir(RtdestR7Rttmpdirttmpfntbtype((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt
_getbundle>
s	













cK@s�|j}|j
d
�
r6t|j
d
�
�
j�}n]|jtd�
�

|j|
|d|jdd�}|jdd�}|j|�

|j	�
|S(s�obtain the body of the introduction message and return it

    This is also used for the body of email with an attached bundle.

    The body can be obtained either from the command line option or entered by
    the user through the editor.
    R0s7
Write the introductory message for the patch series.

trepopathtactiont
patchbombbodyslast-email.txttwb(
RR3topentreadRGR
teditR�tvfstclose(RtdefaultbodytsenderR7RRXtmsgfile((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt_getdescriptionV
s	


	




cK@s.
|j}t
j|�
}|jd
�
p6t|dd�}t|d|
|�}tj�}|r�|jt
j	||||jd�
��

nt
jdd�}	|	j|�

d|jd	d
�}
|	j
ddd
tj|
�
�

tj|	�

|j|	�

t
j||||jd�
�|d<||dfg
S(s�Get the full email for sending a given bundle

    This function returns a list of "email" tuples (subject, content, None).
    The list is always one message long in that case.
    R`sSubject:sA bundle for your repositoryRUR\tapplicationsx-mercurial-bundles%s.hgt
bundlenameR�sContent-DispositionR^tfilenameRaN(RRRtR3R.R�RgRhRWRit	emimebasetMIMEBasetset_payloadt
add_headerRRpt
emailencoderst
encode_base64RrR (RR�R�R7RRtR�RXRytdatapartR�((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt_getbundlemsgsl
s"	





+










%
c	K@s8
|j}t
j|�
}t|||j�|jd
�
dt|�
dt�
}|jd�
put|dd|dd�}|s�dS|d	|}d}	|jd
�
r�t
jt|g��
}
d|
}	nd}
t
||	|
|�}	t
j||	||jd�
�}t
j||||jd�
�|d
<|||
fS(s�make an introduction email, asking the user for content if needed

    email is returned as (subject, body, cumulative-diffstat)R@iRRR`s(optional) Subject: R/RRUR;RZs

R\RaN(RRRtRTtlastR3ROR4R.R R
RZtsumR�RiRr(RR�R�tpatchesR7RRtRR�RXRZRy((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt
_makeintro�
s&	









!


cK@sl
tj
|�
}|j}tj|�
}tt|||��
}g}	|jtd
�
t	|�
�

t
||t	|�
�r�t||
|||�}
|
r�|	j|
�

q�nt	|	�
t	|�
dk}d}t	|�
t	|�
ks�t�
xztt||��
D]c\}
\}}|r&
||
}nt|||||||
dt	|�
||�
}
|	j|
�

q

W|	S(s�return a list of emails from a list of patches

    This involves introduction message creation if necessary.

    This function returns a list of "email" tuples (subject, content, None).
    s+this patch series consists of %d patches.

i
N(RtbyteskwargsRRRttlistR�RGR
ROR:R�R&R tAssertionErrort	enumeratetzipR�(RR�R�t
patchnamesR7t	bytesoptsRRtR�tmsgsRyRRR?t
iR�Rz((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt
_getpatchmsgs�
s*
	








(





cC@s�|j}|j
|
pd
|
p!d�}tj|�
d}|jtd�
tj|�
�

g|D]}|dkra|^qa}|s�|jj	�g
}n|j
d|
p�d|�}|s�|jtd�
�

n|S(s4Return the revisions present locally but not in destsdefault-pushRiscomparing with %s
soutgoing(%s) and ::%ldRUsno changes found
(Rt
expandpathRtparseurltstatusR
Rthidepasswordt	changelogttiprevR�(RR�R�RturlR�((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt_getoutgoing�
s	


 %





cC@s;tj
tj��
}tjjd
|�}d||
|fS(Nt
HGHOSTNAMEs
<%s.%d@%s>(Rt
strtolocaltsockettgetfqdntenvironR3(R	t	timestampthostname((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt_msgid�
s


RURXs-send patches as inline message text (default)t
aRWssend patches as attachmentsR�R[s"send patches as inline attachmentss/email addresses of blind carbon copy recipientstEMAILt
cs"email addresses of copy recipientss#ask for confirmation before sendingt
dRZsadd diffstat output to messagestdates&use the given date as the sending datetDATER0s,use the given file as the series descriptiontFILEt
fsemail address of sendert
nR\s!print messages that would be sentt
mtmboxs3write messages to mbox file instead of sending thems)email addresses replies should be sent tot
sR`s0subject of first message (intro or single patch)tTEXTsin-reply-tosmessage identifier to reply totMSGIDR@s flags to add in subject prefixestFLAGR|semail addresses of recipientstemailt
gR�suse git extended diff formatRYsomit hg patch headert
otoutgoings/send changes not found in the target repositoryt
bR�s-send changes not in target as a binary bundlet
Btbookmarks-send changes only reachable by given bookmarktBOOKMARKR�s"name of the bundle attachment filetNAMER�RJsa revision to sendtREVtforces?run even when remote repository is unrelated (with -b/--bundle)tbasesGa base changeset to specify instead of a destination (with -b/--bundle)s-send an introduction email for a single patchshg email [OPTION]... [DEST]...thelpcategoryc6@s8tj
�
�
�
tj��
��
jd
�
}�
jd�
}�
jd�
}�
jd�
}�
jd�
}�
jd�
}	�
jd�
p�|s�tj��

n|p�|p�|p�|p�|	s�tjtd�
�
�
n|r�|r�tjtd	�
�
�
n|r
|	r
tjtd
�
�
�
n|s'
|rs
t	|�
dkrQ
tjtd�
�
�
n|rd
|d
}
ndR}
g}n|r�
|r�
tjtd�
�
�
n|}nF|	r�
|	|
jkr�
tjtd�
|	�
�
ntj
|
|	�}ntj|
|�}|rt|
|
|�}n|r=g|D]}d|^q �
d<n|
jjdd�}|r'|
jjd�

ytj|
i|�}
Wn1tjk
r�


|
jjtd�
|�

�n
X|
jd�
s�|
jjd�

q'g|D]}|
|^q�}|
jd�|D�
�
}g}x4t|�
D]&\}}||s |j|�

q q W|r't	|�
dkr�td�
}|||d
t	|�
df;}n td�
}|||d
f;}g|D]}|j�^q�}djd�|
jd|�D�
�
}td�
||f}tj|d|�

�
q'n|r?tj|�
�ntj ���f
d �}�
jd!�
p��jd"d!�p��jdd!�p�t!�d#�j"��}|rtj#�
�
}t$|
|
|�}|j%�}|j&d
dR�
t'|
|||�}nt(|
||tj#�
�
�}g�t)dR��
��fd$�}|d%d&t*�

}|srtjtd'�
�
�
n|d(d&t*d)d*�
} |d+�
}!|d,�
}"�j+dd-�}#|#t,�
jd.�
p��
jd-�
�
O}#|#r��j-td/�
d0d1�


�j-d2|d0d3�


x%�D]}$�j-d4|$d0d5�


qWxJ|D]B\}%}&}'�j-d6|&d0d7�


|'rA�j-|'d0d8�


qAqAW�j-d9�

�j.td:�
�
r�tjtd;�
�
�
q�n�j-d9�

�
jd<�
p�dR}(|(dRk	r-|(j/d=�
sd=|(}(n|(j0d>�
s-|(d>7}(q-nt1j2t3j4|�
�
d})tj5�|��
jd�
�}dR}*dR}+�j6td?�
d@tdA�
dBt	|�
�
},x�t|�
D]v\}-\}%}&}'y5||%dC�
|%dD<|+s�|%dD}+n|+|%dE<Wn!t7k
r


|d�
|%dD<n
X|(r;|(|%dF<|(|%dG<n|(sNdC|%kr[|%dD}(ndHt8j9�|%dI<t1j:�d
dJt*�

|%dK<�d
d�df�||%d#<dLj|�
|%d%<| r�dLj| �
|%d(<n|!r�dLj|!�
|%d+<n|"r	dLj|"�
|%d,<ntj;r�	x�t<|%j=��
D]�\}.}/t)}0t>|.t?�rq	|%|.=tj@|.�
}.t*}0nt>|/t?�r�	tj@|/�
}/|0s�	|%|.=nt*}0n|0r1	|/|%|.<q1	q1	Wn�
jd�
r[
�jAtdM�
|&dN�
�jBd"�

tC�dOt)�

}1y!|1jD|%d
�
�j-d9�

Wq&tEk
rW

}2
|2jFtFjGkrX
�qX
q&Xq�|*sy
tjH�d|�

}*n�jAtdP�
|&dN�
|,jI|-dQ|&�


|s�
|%d+=ntJ�}3tC|3dOt)�

}1|1jD|%d
�
||!| }4g|4D]}5t3j4|5�
^q�
}4|*|)|4|3jK��
q�W|,jL�
dRS(SsQsend 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]" 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 parts. First, the changeset
    description.

    With the -d/--diffstat option, if the diffstat program is
    installed, the result of running diffstat on the patch is inserted.

    Finally, the patch itself, as generated by :hg:`export`.

    With the -d/--diffstat or --confirm options, you will be presented
    with a final summary of all messages and asked for confirmation before
    the messages are sent.

    By default the patch is included as text in the email body for
    easy reviewing. Using the -a/--attach option will instead create
    an attachment for the patch. With -i/--inline an inline attachment
    will be created. You can include a patch both as text in the email
    body and as a regular or an inline attachment by combining the
    -a/--attach or -i/--inline with the --body option.

    With -B/--bookmark changesets reachable by the given bookmark are
    selected.

    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. Use the ``patchbomb.bundletype`` config option to
    control the bundle type as with :hg:`bundle --type`.

    With -m/--mbox, 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.

    With -n/--test, all steps will run, but mail will not be sent.
    You will be prompted for an email recipient address, a subject and
    an introductory message describing the patches of your patchbomb.
    Then when all is done, patchbomb messages are displayed.

    In case email sending fails, you will find a backup of your series
    introductory message in ``.hg/last-email.txt``.

    The default behavior of this command can be customized through
    configuration. (See :hg:`help patchbomb` for details)

    Examples::

      hg email -r 3000          # send patch 3000 only
      hg email -r 3000 -r 3001  # send patches 3000 and 3001
      hg email -r 3000:3005     # send patches 3000 through 3005
      hg email 3000             # send patch 3000 (deprecated)

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

      hg email -B feature       # send all ancestors of feature bookmark

      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

      hg email -o -m mbox &&    # generate an mbox file...
        mutt -R -f mbox         # ... and view it with mutt
      hg email -o -m mbox &&    # generate an mbox file ...
        formail -s sendmail \   # ... and use formail to send from the mbox
          -bm -t < mbox         # ... using sendmail

    Before using this command, you will need to enable email in your
    hgrc. See the [email] section in hgrc(5) for details.
    R�R�R�R�RJR�R\s0specify at least one changeset with -B, -r or -osE--outgoing mode always on with --bundle; do not re-specify --outgoings -r and -B are mutually exclusivei
stoo many destinationsis)use only one form to specify the revisionsbookmark '%s' not founds%dR�RRs0checking that revision exist in the public repo
s!unable to access public repo: %s
tknowns/skipping existence checks: public repo too old
c
s@s|]}
|
j�V
qdS(
N(
R	(t.0t
h((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pys	<genexpr>�ss'public "%s" is missing %s and %i othersspublic url %s is missing %sR;c
s@s|]}
d|
V
qd
S(s-r %sN((R�R�((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pys	<genexpr>�s
s
heads(%ld)suse 'hg push %s %s'thintc

@st|d
 t
�d�
�S(Nii(R�tint(
tid(
t
start_time(s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pytgenmsgid�s
RR�tFromc@sY
|j�}|j
d
d�j�}�
j|�
}|rx�jd|dj|�
f�

tj�|��
jd�
�S�jd|�p��jd|�}|s��jd|�p��jd|�}|r�|
r�t	�|d|�
}q�n|r-
�jd||f�

tj�|g
��
jd�
�S|rU
tj�|g
��
jd�
�SgS(	Nt
-R
s%s: %ss, R\R�RR(
tlowertreplaceR3R&RARtaddrlistencodeRt	hasconfigR.(theadertaskRt	configkeytopttaddrstaddrt	specified(RtR7t	showaddrsR(s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pytgetaddrs�s(




 










"



tToR�sno recipient addresses providedtCcRRUtBccsReply-ToRRZs
Final summary:

tlabelspatchbomb.finalsummarys	From: %s
spatchbomb.froms%s
spatchbomb.tosSubject: %s
spatchbomb.subjectspatchbomb.diffstatss

s1are you sure you want to send (yn)?$$ &Yes $$ &Nospatchbomb canceledtin_reply_tot
<t
>tsendingtunittemailsRQsX-Mercurial-Nodes
Message-IdsX-Mercurial-Series-IdsIn-Reply-Tot
ReferencessMercurial-patchbomb/%ss
User-Agentt	localtimetDates, sdisplaying s ...
tmangle_from_ssending titemN(MRR�RRtR3tvalidateconfigRtAbortR
ROR t
_bookmarksR
tbookmarkrevstrevrangeR�RRtdebugRtpeert	RepoErrorR6tcapableR�R�R&RJRAtsetRt	parsedatetmakedateR.tusernamet	strkwargsR�tcopyRfR�R�R5R4t
configbooltboolRGtpromptchoiceRbRnteutilt	parseaddrRRpt
addressencodetmakeprogresst	TypeErrorRtversiont
formatdatetispy3R�titemst
isinstancetbyteststrurlR�tpagert_bytesgeneratortflattentIOErrorterrnotEPIPEtconnecttupdateRBRItcomplete(6RRR�R7R�R�R�R�RJR�R�R�Rt
publicpeerRLR�tmissingRPR�RyR"tmissingrevstrevhintR�R�R�tstroptst
bundledatat
bundleoptsR�R
RRRtreplytoRR

R�R�Rwtparenttsender_addrtsendmailt
firstpatchtprogressR�thdrtvaltchanget	generatortinsttfptalldestsR�((RtR7R
R�Rs5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyR��
sZ
h













	


	







$



















$






!











(


















!


-
"


























	





	




	



















	



"
(Jt__doc__t
__future__Rtemail.encoderstencodersR�temail.generatorRK
temailgentemail.mime.basetmimeR�R�temail.mime.multipartt	multipartRgtemail.utilstutilsR&
R6
R�R�tmercurial.i18nR
t	mercurialRRRRRRRR	RkR
RRR
RRtmercurial.utilsRRBtcmdtabletcommandtconfigtablet
configitemR R5R-
tBytesGeneratorR3
t	Generatort
testedwithR#R(R,R.R:RNRTR�R�R�R�R�R�R�R�R�t	emailoptst
remoteoptstCATEGORY_IMPORT_EXPORTR�(((s5/usr/lib64/python2.7/site-packages/hgext/patchbomb.pyt<module>Is�








^
	











	
		
				
	
O					%		


	





	



	

	

	



$�