a &0É_Ž{ã@sdZddlmZddlmZddlmmZ ddl mm Z ddl mZddlZddlZddlZddlmZddlmZddlmZmZmZmZmZmZmZmZ m!Z!m"Z"m#Z#m$Z$m%Z%m&Z&ddl'm(Z(e&j)Z)iZ*e# +e*¡Z+iZ,e# -e,¡Z-e-dd dd e-dd dd e-dd dd e-dd dd e-dddd e-dddd e-dddd e-dddd e-dddd e-dddd dZ.dd„Z/dd„Z0dd„Z1d„dd„Z2d d!„Z3d"d#„Z4d$d%„Z5d…d&d'„Z6d(d)„Z7d*d+„Z8d,d-„Z9d.d/„Z:d0d1„Z;d†d2d3„Zd8d9ded:ƒfd;dd?ded@ƒfd8d gedAƒedBƒfdCd gedDƒedBƒfd8d dedEƒfdFdGdedHƒfd8dId8edJƒedKƒfd8dLd8edMƒedNƒfdOdd8edPƒedBƒfdQdRdedSƒfdTdUd8edVƒedNƒfd8dgedWƒedBƒfdXdYd8edZƒed[ƒfd8d\d8ed]ƒed^ƒfd8d_ged`ƒedaƒfdbdgedcƒedBƒfgZ?e+dddedfdedgƒfd8dhdediƒfdjdkdedlƒfdmdndedoƒfdpdqd8edrƒedsƒfd8dtdneduƒedvƒfdwdxgedyƒedzƒfd8d{ded|ƒfd8d}ged~ƒedzƒfd8ddedƒfg e?ej@ed€ƒe+jAdd‚dƒ„ƒZBdS)‡as 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 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. é)Úabsolute_importN)Ú_)Úopen)ÚcmdutilÚcommandsÚencodingÚerrorÚ formatterÚhgÚmailÚnodeÚpatchÚpycompatÚ registrarÚscmutilÚ templaterÚutil)Údateutiló patchbombó bundletype©ÚdefaultsbccsccóconfirmFó flagtemplateófromóintroóautoó publicurlsreply-tostosships-with-hg-corecCs,| ¡}|j dd¡}|r(d|||fSdS)zKAdd a header pointing to a public URL where the changeset is available rrs/Available At %s # hg pull %s -r %sN)ÚrepoÚuiÚconfig)ÚseqÚctxrÚ publicurl©r$ú1/usr/lib/python3/dist-packages/hgext/patchbomb.pyÚ_addpullheader–sýr&cCstj d¡ttjd<dS)Nspullurl)rZ extraexportÚappendr&Zextraexportmap)rr$r$r%Úuisetup§s r(cCs| ¡s dS|j d¡dS)Nólast-email.txt)ZlocalZ_wlockfreeprefixÚadd)rrr$r$r%Ú reposetup¬sr+ó:cCs |r|d|7}| |||¡S)Ns [%s])Úprompt)rr-rÚrestr$r$r%r-²s r-cCs€| dd¡}| d¡s | d¡r&d}nV|dkr4d}nH|dkrBd}n:|dkrT|d k}n(| td ƒ|¡| td ƒ¡|d k}|S) z-is an introductory message apparently wanted?rródescTsalwayssneverFrés,warning: invalid patchbomb.intro value "%s" s'(should be one of always, never, auto) )r ÚgetÚ write_errr)rÚoptsZnumberZ introconfigZintror$r$r%Ú introwanted¸s   ÿr4c Csœ| dd¡}|sd |¡St ¡}t t |¡¡}t ||di|¡@}|  ¡|j ||d|  dd|j |dd ¡Wd ƒn1sŠ0Y|  ¡S) z(build flag string optionally by templaterró s patchbombflag)r"sflagss%sóflag)ÚnameN)r ÚjoinrÚstringior Zliteral_templatespecrZ unquotestringZtemplateformatterZ startitemÚcontextÚwriteZ formatlistÚgetvalue)rrÚrevÚflagsZtmplÚoutÚspecZfmr$r$r%Ú _formatflagsÌs  6rAc CsFt||||ƒ}|rd|}|s&d|Std|ƒ}d||||fSdS)zbuild prefix to patch subjectr5s [PATCH%s]ó%ds[PATCH %0*d of %d%s]N)rAÚlen) rrr=r>ÚidxÚtotalÚnumberedÚflagZtlenr$r$r%Ú _formatprefixÚs rHc  Csæg} d} d} |D]H} |  d¡r6|  d¡r|  ¡d} q|  d¡sJ|  d¡rNqZ|  | ¡q| sf| sft‚| d¡rœ| d¡sœd  | d d…¡ ¡p’d } | d 7} | d ¡rî|rÄ|d d¡rÄ| d¡q¦|rÒ| d¡|rî|d ¡sî| d¡qÒt  |¡}| d¡r| |d7} | d¡p$| d¡}|r8| d¡rF| d  |¡7} |r,t   ¡}| rv|  t  || || d¡¡¡t  d  |¡d| d¡¡}t | ¡}| södd„| |¡Dƒ}|rÄ|d} n2|d krætj|| d||d} nt || d¡} d}| d¡r d}|dt | ¡|d<|  |¡nt j| | d¡d}t|||| d¡|||ƒ}| d ¡ d ¡}|sŽd! || d"¡p†|g¡}nd! ||g¡}t  |||| d¡¡|d#<t | ¡|d$<d%||d&<d%||d'<|||fS)(Nóó#s # Node IDéÿÿÿÿsdiff -rs diff --gitóattachóbodyó r0s"Patch subject is complete summary.s óplainrs# ódiffstats óinlineótestzx-patchcSs$g|]}| d¡s| d¡r|‘qS)s.patchs.diff)Úendswith)Ú.0Útr$r$r%Ú %sþzmakepatch..s %b-%n.patch)ZseqnorEs%b.patchZinlineÚ attachmentz ; filename=úContent-Disposition)Zdisplayr6s. r5ósubjectÚSubjectúX-Mercurial-Nodez%izX-Mercurial-Series-IndexzX-Mercurial-Series-Total)Ú startswithÚsplitr'Ú ValueErrorr1r8ÚstripÚpopr ÚdiffstatÚemimemultipartÚ MIMEMultipartÚattachr Ú mimeencodeZ mimetextpatchÚnodemodÚbinZnodetagsrZ makefilenamerÚ strfromlocalrHÚrstripÚ headencoderZsysstr)rrr=Z patchlinesr3Ú _charsetsrDrErFZ patchnameÚdescr ÚbodyÚlineÚdsZ addattachmentÚmsgÚpZbinnodeZ patchtagsZ dispositionÚprefixÚsubjr$r$r%Ú makepatchçsŠ     þ       ÿ þ   ÿ ÿ ÿ  rtc ks„|j}|d ¡}|D]h}||krH|d ¡s:|d ¡rH| tdƒ¡tƒ}tj||g|t j ||ddd|  ¡  d¡VqdS)zlreturn a list of patches for a list of revisions Each patch in the list is itself a list of lines. ó.Ns3warning: working directory has uncommitted changes T)Zgit)r3rN) rr=ÚfilesZdeletedÚwarnrr9rZ exportfiler Zdifffeatureoptsr<r])rÚrevsr3rÚprevÚrÚoutputr$r$r%Ú _getpatchesKs  ÿr|cKsê|j}tjdd}tj |d¡}| dd¡}|r8||d<z~tj||||fi|¤Žt   |¡Wzt  |¡Wnt y|Yn0t  |¡Szt  |¡Wnt yªYn0t  |¡n.zt  |¡Wnt yØYn0t  |¡0dS)zÝ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. shg-email-bundle-)rróbundlerrÚtypeN)rrZmkdtempÚosÚpathr8r rÚbundlerZreadfileÚunlinkÚOSErrorÚrmdir)rÚdestr3rZtmpdirZtmpfnZbtyper$r$r%Ú _getbundle\s2     ú  ü r†cKsh|j}| d¡r$t| d¡ƒ ¡}n@| tdƒ¡|j|||jdd}| dd¡}| |¡|  ¡|S)zõ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. rls7 Write the introductory message for the patch series. s patchbombbody)ZrepopathÚactionr)swb) rr1rÚreadr;rZeditr€ZvfsÚclose)rZ defaultbodyÚsenderr3rrmZmsgfiler$r$r%Ú_getdescriptionus ÿ ÿ  r‹c KsØ|j}t |¡}| d¡p$t|ddƒ}t|d|fi|¤Ž}t ¡}|rb| t  |||| d¡¡¡t   dd¡} |   |¡d| d d ¡} | j d d t | ¡d t | ¡| | ¡t |||| d¡¡|d<||dfgS)z¶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. ÚsubjectsSubject:sA bundle for your repositoryrIÚtestZ applicationzx-mercurial-bundles%s.hgÚ bundlenamer}rXrW)ÚfilenamerZN)rr rkr1r-r‹rbrcrdreÚ emimebaseZMIMEBaseZ set_payloadZ add_headerrrhÚ emailencodersZ encode_base64rj) rrŠrr3rrkrsrmrpZdatapartrŽr$r$r%Ú_getbundlemsgsŽs*  ÿ  ý  r’c KsÜ|j}t |¡}t||| ¡| d¡dt|ƒdd}| d¡pLt|d|dd}|sVd S|d |}d} | d ¡rŠt  t |gƒ¡} d | } nd } t || |fi|¤Ž} t  || || d ¡¡} t  |||| d ¡¡| d<| || fS)z€make an introduction email, asking the user for content if needed email is returned as (subject, body, cumulative-diffstat)rGrT)rFrŒs(optional) Subject: rI)r.rNr5rarNrrZ)rr rkrHZlastr1rCr-r raÚsumr‹rerj) rrŠrxÚpatchesr3rrkrrrsrmrarpr$r$r%Ú _makeintro¬s( ÿ ÿ   r•c Kst |¡}|j}t |¡}tt||fi|¤Žƒ}g} | tdƒt |ƒ¡t ||t |ƒƒr~t ||||fi|¤Ž} | r~|   | ¡t | ƒt |ƒdk} d} t |ƒt |ƒksªJ‚t t||ƒƒD]D\} \}}|rÐ|| } t||||||| dt |ƒ| | ƒ } |   | ¡q¸| S)zÀ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. r0N)rÚ byteskwargsrr rkÚlistr|r;rrCr4r•r'Ú enumerateÚziprt)rrŠrxZ patchnamesr3Z bytesoptsrrkr”ÚmsgsrprFr7Úirzrqr$r$r%Ú _getpatchmsgsÍs<   ö rœcCs†|j}| |pd|pd¡}t |¡d}| tdƒt |¡¡dd„|Dƒ}|s^|j  ¡g}|  d|pjd|¡}|s‚| td ƒ¡|S) z4Return the revisions present locally but not in dests default-pushsdefaultrscomparing with %s cSsg|]}|dkr|‘qS)rr$©rTrzr$r$r%rVrIz _getoutgoing..soutgoing(%s) and ::%ldrIsno changes found ) rZ expandpathr ZparseurlÚstatusrrZ hidepasswordZ changelogZtiprevrx)rr…rxrZurlr$r$r%Ú _getoutgoingüs rŸcCs>zt tjd¡}Wnty.t ¡}Yn0d|||fS)Ns HGHOSTNAMEz <%s.%d@%s>)rrhÚenvironÚKeyErrorÚsocketZgetfqdn)r Z timestampZhostnamer$r$r%Ú_msgid s  r£rIrMs-send patches as inline message text (default)óarLssend patches as attachmentsóirQs"send patches as inline attachmentss/email addresses of blind carbon copy recipientssEMAILócs"email addresses of copy recipientss#ask for confirmation before sendingódrPsadd diffstat output to messagesódates&use the given date as the sending datesDATEr/s,use the given file as the series descriptionsFILEófsemail address of senderónrRs!print messages that would be sentómómboxs3write messages to mbox file instead of sending thems)email addresses replies should be sent toósrYs0subject of first message (intro or single patch)sTEXTs in-reply-tosmessage identifier to reply tosMSGIDr6s flags to add in subject prefixessFLAGótsemail addresses of recipientsóemailógsgitsuse git extended diff formatrOsomit hg patch headeróoóoutgoings/send changes not found in the target repositoryóbr}s-send changes not in target as a binary bundleóBóbookmarks-send changes only reachable by given bookmarksBOOKMARKs bundlenames"name of the bundle attachment filesNAMEórórevsa revision to sendsREVsforces?run even when remote repository is unrelated (with -b/--bundle)sbasesGa base changeset to specify instead of a destination (with -b/--bundle)s-send an introduction email for a single patchshg email [OPTION]... [DEST]...)Z helpcategoryc0 s–t ˆ¡‰t ˆ¡‰ˆ d¡}ˆ d¡}ˆ d¡}ˆ d¡}ˆ d¡}ˆ d¡} ˆ d¡sh|sht ˆ¡|sŠ|sŠ|sŠ|sŠ| sŠt tdƒ¡‚|r |r t td ƒ¡‚t   ˆdd¡|s¶|ræt |ƒd krÐt td ƒ¡‚|rÞ|d } nd } g}|r|rþt tdƒ¡‚|}n0| r4| ˆj vr(t tdƒ| ¡‚t  ˆ| ¡}t  ˆ|¡}|rRtˆ| |ƒ}|rjdd„|Dƒˆd<ˆj dd¡} | rΈj d¡zt ˆi| ¡} Wn,tjyȈj tdƒ| ¡‚Yn0|  d¡säˆj d¡nê‡fdd„|Dƒ} |  dd„| Dƒ¡}g}t| ƒD]\}}||s| |¡q|rÎt |ƒd krntdƒ}|| |d t |ƒd f;}ntdƒ}|| |d f;}dd„|Dƒ}d d d„ˆ d!|¡Dƒ¡}td"ƒ| |f}tj||d#‚|ràt |¡‰nt  ¡‰‡fd$d%„}ˆ d&¡p*ˆ d'd&¡p*ˆ dd&¡p*t!ˆd(ˆ "¡ƒ}|rxt #ˆ¡}t$ˆ| fi|¤Ž}| %¡}| &d)d ¡t'ˆ||fi|¤Ž}nt(ˆ||fit #ˆ¡¤Ž}g‰da‡‡‡‡fd+d,„ }|d-d.d/}|sÊt td0ƒ¡‚|d1d.d2d3}|d4ƒ}|d5ƒ} ˆ )dd6¡}!|!t*ˆ d7¡p ˆ d6¡ƒO}!|!rºˆj+td8ƒd9d:ˆj+d;|dd:q@|D]2\}#}$}%ˆj+d?|$d@d:|%r^ˆj+|%dAd:q^ˆ +dB¡ˆ ,tdCƒ¡rºt tdDƒ¡‚ˆ +dB¡ˆ dE¡pÒd }&|&d urt- .|&¡}&|& /dF¡südF|&}&|& 0dG¡s|&dG7}&t1 2t- .|¡¡d }'t 3ˆ|ˆˆ d¡¡}d }(d })ˆj4tdHƒtdIƒt |ƒdJ}*t|ƒD] \}+\}#}$}%z*||#dKƒ|#dL<|)s–|#dL})|)|#dM<Wn t5yÀ|dNƒ|#dL<Yn0|&rØ|&|#dO<|&|#dP<|&rèdK|#vrð|#dL}&dQt6 7¡ 8¡|#dR<t1j9ˆd d.dS|#dT<ˆd d ˆd f‰||#dU<dV |¡|#dW<|rXdV |¡|#dX<|rldV |¡|#dY<| r€dV | ¡|#dZ<ˆ d¡r ˆ :td[ƒ|$d\¡ˆ ;d'¡tj<ˆd*d]},z|, =|#d*¡ˆ +dB¡Wn6t>y}-z|-j?t?j@krò‚WYd }-~-n d }-~-00n||(stjAˆ|d^}(ˆ :td_ƒ|$d\¡|*jB|+|$d`|sJ|#dY=tCƒ}.tj<|.d*d]},|, =|#d*¡|||}/|(|'|/|. D¡ƒqf|* E¡d S)baQsend 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²r·rµrRs0specify at least one changeset with -B, -r or -osE--outgoing mode always on with --bundle; do not re-specify --outgoingr0stoo many destinationsrNs)use only one form to specify the revisionsbookmark '%s' not foundcSsg|] }d|‘qS)rBr$rr$r$r%rVrIzemail..srevsrrs0checking that revision exist in the public repo s!unable to access public repo: %s sknowns/skipping existence checks: public repo too old csg|] }ˆ|‘qSr$r$r)rr$r%rV*rIcss|]}| ¡VqdS)N)r ©rTÚhr$r$r%Ú +rIzemail..s'public "%s" is missing %s and %i othersspublic url %s is missing %scSsg|] }| ¡‘qSr$)r=)rTr"r$r$r%rV7rIr5css|]}d|VqdS)s-r %sNr$r¸r$r$r%rº8ss heads(%ld)suse 'hg push %s %s')Úhintcst|dd…tˆdƒƒS)Nér)r£Úint)Úid)Ú start_timer$r%ÚgenmsgidDszemail..genmsgidrr¯sFromrFcsì| ¡}| dd¡ ¡}ˆ |¡}|rTˆ d|d |¡f¡t ˆ|ˆˆ d¡¡Sˆ d|¡pjˆ d|¡}|sžˆ d|¡p†ˆ d|¡}|sž|ržt ˆ||d}|r̈ d||f¡t ˆ|gˆˆ d¡¡S|rèt ˆ|gˆˆ d¡¡SgS) Nó-ó_s%s: %ss, rRr¯rr) ÚlowerÚreplacer1r'r8r Zaddrlistencoder Z hasconfigr-)ÚheaderÚaskrZ configkeyZoptZaddrsÚaddrZ specified)rkr3Ú showaddrsrr$r%ÚgetaddrsZs. ÿÿÿzemail..getaddrssToT)rÆsno recipient addresses providedsCcrI)rÆrsBccsReply-TorrPs Final summary: spatchbomb.finalsummary)Zlabels From: %s spatchbomb.froms%s s patchbomb.tos Subject: %s spatchbomb.subjectspatchbomb.diffstatsrNs1are you sure you want to send (yn)?$$ &Yes $$ &Nospatchbomb canceleds in_reply_toú<ú>ssendingsemails)ZunitrEr[z Message-IdzX-Mercurial-Series-IdZ patchbombz In-Reply-ToZ ReferenceszMercurial-patchbomb/%sz User-Agent)Ú localtimeZDateZFromz, ZToZCcZBcczReply-Tos displaying s ... )Z mangle_from_)Úmboxssending )Úitem)FN)Frr–r rkr1ZvalidateconfigrZAbortrrZcheck_at_most_one_argrCZ _bookmarksrZ bookmarkrevsZrevrangerŸrr Údebugr ZpeerZ RepoErrorr2ZcapableÚknownr˜r'r8ÚsetrZ parsedateZmakedater-ZusernameZ strkwargsr†Úcopyr`r’rœZ configboolÚboolr;Z promptchoicerrhr\rSÚeutilZ parseaddrZ addressencodeZ makeprogressÚ TypeErrorrÚversionÚdecodeZ formatdateržZpagerÚ GeneratorZflattenÚIOErrorÚerrnoZEPIPEZconnectÚupdater9r<Zcomplete)0rrrxr3rÚdaterÍZoutgoingr=Zbookmarkr…r#Z publicpeerr?rÐZmissingrDr¹rpZ missingrevsZrevhintr»rÀrŠZstroptsZ bundledataZ bundleoptsršrÉÚtoZccZbccZreplytoZconfirmrÇÚmrsroÚparentZ sender_addrZsendmailZ firstpatchZprogressr›Ú generatorÚinstÚfpZalldestsr$)rkr3rrÈr¿rr%ÚemailSs^         ÿÿÿ        ÿ    ÿ    ÿ þü     ÿ     ÿ      rã)Nr,)N)N)CÚ__doc__Z __future__rZemail.encodersZencodersr‘Zemail.mime.baseZmimeÚbaserZemail.mime.multipartZ multipartrbZ email.utilsZutilsrÔrÚrr¢Zmercurial.i18nrZmercurial.pycompatrZ mercurialrrrrr r r r rfr rrrrrZmercurial.utilsrr9ZcmdtableZcommandZ configtableZ configitemZ testedwithr&r(r+r-r4rArHrtr|r†r‹r’r•rœrŸr£Z emailoptsZ remoteoptsZCATEGORY_IMPORT_EXPORTrãr$r$r$r%Ús\B     @   ÿÿÿÿÿÿÿÿÿÿ ö d! / ûûûûûûûÅ?üüûûÿü ÿø üÏ8È9Ç:Ã?