Þ•GT²·ŒdhÛ!iÛ!‹Û#­Û#ÑÛ4õÛ3*Ü-^Ü-ŒÜºÜ@ÏÜTÝeÝ„Ý8¡Ý8ÚÝDÞ8XÞ<‘Þ>ÎÞ0 ß(>ß>gßH¦ßïß à'à;<à$xà/àFÍàBáFWá/žá.Îáýáâ+â>âANâTâŒåâ5rã3¨ãÜã÷ã ä%ä8äWä*nä™ä¶äÑäàäñä å å"9å\å'oå —å¢å4¼åñåÍöåOÄæ|è°‘é Bêãêëœë ¼ëœ]ìtúìjoí2Úí2 î‘@îUÒîé(ï+ð->ðlð†ðS¡ð:õð40ñeñ‰ñ8 òEDòŠò¦ò"Äòçòó5$ó0Zó9‹ó@Åó,ô:3ô+nô,šô)Çô-ñô'õ+GõÃsõ7ö2Oö4‚ö)·ö!áö$÷)(÷!R÷t÷÷.¢÷$Ñ÷/ö÷&ø#<ø`ø=zø¸ø1ÎøAù.Bù9qùJ«ù)öùG ú2hú›ú-µú0ãúû+2û!^û €û1¡ûÓûíûü3ü,Nü{ü.—ü%Æü$ìü#ýF5ý'|ý+¤ýÐýäý3øý0,þ-]þ?‹þ)Ëþ*õþ ÿ?ÿXÿxÿ9ÿfÊÿ‚1y´^.Y çPˆ8Ù‡šõ«ê¡»ŒäH(-V†vXýÁV¡ ñº ö¬ L£ Êð » ÀÌ Ç ¹U°jÀ4+\`ǽ¦…ñ,`„­/²OâN2A"Ã'æ^8mw¦ZMy3Ç:ûX6.<¾7ûL3e€7æ:DY?ž5Þ@JU= rÞ(Q%zG ,èJ 4` L• *â L !.Z!6‰!AÀ!7"::";u"E±"c÷":[#4–#2Ë#:þ#)9$&c$?Š$EÊ$C%HT%1%FÏ%6&#M&/q&¡&%Á&4ç&&'ŽC'vÒ'7I(6(3¸(.ì(/)\K)*¨):Ó)D*\S*n°*D+Od+ˆ´+@=,A~,'À,0è,4-MN-Nœ-Xë-LD.6‘.BÈ.Z /gf/TÎ/'#0úK00F1Íw1aE3°§3™X4nò4{a5Ý5Án6÷07$(8"M8Úp8K9âb9E:M;x];hÖ<€?=®À=°o> ?ã±?h•@Oþ@NNAA¹²A=lBYªBQC=VC ”D§žE$FFÇkHA3I:uK‰°K!:L3\LM3¦NóÚO.ÎP.ýP!,QNQ*iQ/”Q]ÄQ("R[KR=§RÃåR(©SÒS ðST!1T~ST:ÒT Uñ,VSW,rW§ŸWPGXP˜XùéXoãY>SZY’ZœìZ]‰[ç[ü[Ý\(î\]¬^mÊ^ä8_–a´´aRib”¼bIQc›d¹»d‹ueÑfÓgEëh1i5PiN†i3Õi% jI/jmyjÖçjH¾kÒl Úlì{mœhnppºvp¸1q êq÷öróît$âv‚x2ŠxM½yZ { f|‚‡}š i¥Å€HÕ€¢¡Á[c‚[¿‚Sƒ£oƒ®„c„x&…jŸ…^ †^i†_Ȇ(‡æ0ˆ'‰!?‰a‰‰¨Ÿ‰qHŠ/ºŠ*ꊗ‹é­‹K—Œè㌌Ì)YŽ7ƒŽI»Ž;„AöƲ½bp’=Ó“”~‘”à•¯ñ•ƒ¡–Ý%—˜ ™Ñš.ã› œ3œÃíÆžé´Ÿ»ž ¹Z¡¿¢*Ô¢Þÿ£[Þ¤{:¥’¶¥½I¦§§¯§>ͧl ª(yª‚¢ª|%«¢«¿«¬k­†­û®H‰°?Ò°Y±vl²„ã²Fh³—¯³ÔG´Þµ ûµ<·C·b[· ¾·5Ë·(¸2*¸1]¸$¸%´¸&Ú¸F¹6H¹(¹'¨¹3й!º4&º[º jº »ô‹»‼<c½‘ ½›2¾÷ξTÆ¿_À!{ÀBÀàÀWæÁ>ÂM\Â5ªÂtàÃ+UÄÕÄ[WŘ³ÅÍLÇVÈÞqÈlPÉʽÉrˆÊŒûÊ‘ˆËŒÌh§ÌfÍëwÍžcÎkÏZnÏÉÏžIÐ’èÐï{ÒmkÓ^ÙÓÖ8Ô…Õ˜•ÕÃ.Ö´òÖϧדwØe ÙÎqÙØ@Ú¼ÛaÖÛ<8ÜkuÜmáÜeO݇µÝ°=ÞMîÞs<ß °ß¬½àéjáTâƒUã‚Ùã3\ä|åF æ¹TçàèóïèÐã郴ê8ëc?ì³£ìWîufï Üï¤çðæŒòüsôapõ`Òõ•3öjÉöz4øF¯øköøqbù…ÔùvZúbÑúo4ûz¤ûÃüqãü>Uý”þ³•ÿQIÆ›fb±É¦{Y"3|)°…ÚÌ`Ç-õ:³O, Ë0 ü K Mg áµ ,— Ä WÚ µ2„èƒm+ñâObP«³T_P´YV_U¶' P4‡…‘ cŸ"§&ÌÎX›ôºõj°>©Pè79‹q8ýk6 9¢ ‹Ü Oh!à¸!}™"/#VG#ž$J½$H%HQ%Hš%ã%&/&4D&7y&'±&9Ù&@'JT'!Ÿ'>Á'>(3?(Cs(C·(Eû(=A);)5»)Bñ)/4*Yd*W¾*@+?W+¡—+D9,~,˜,,·,9ä,--2-L`-E­-fó-WZ.B².Cõ.H9/6‚/f¹/7 0iX0TÂ0F1Z^1R¹1A 2KN2Ýš27x3-°3pÞ3EO46•4-Ì4âú4XÝ5Ñ66p7'y75¡77×7²8TÂ8p9¢ˆ9a+:?:3Í:A;'C;.k;%š;$À;/å; <D6<C{<Å¿<$…=eª=Þ?Œï?‹|@ŒAs•B¡ Cf«CäDz÷DnrE\áEå>F›$GÑÀG+’Hw¾HÂ6K{ùKàuL#VMpzN¹ëO©¥PcOQ…³Rw9S+±T*ÝTÝUfæU.MV0|V*­V.ØV‚WŽŠWX@1ZorZkâZcN[)²[&Ü[ä\hè\¡Q]þó]ò^t`4|aý±a"¯bŒÒb|_cÜc8^d——es/fZ£f0þf(/g7Xg8g*Ég~ôg—shò iþj‚k–kj¯lšmiµm½nÈÝn¡¦p™HqBâq:%sÏ`sh0tö™u¡v<2w³ow#xœÁx‡^yæy?|9B|~||>û|#:}^}:î}…)~R¯‘€U”€¥ê€.e¿‚e%ƒ“‹ƒ-„M…ød†v]‡Ô‡vbˆ4Ùˆ‰‰*˜‰÷ÉD»‹…Œ͆Œ?T™”|.ŽQ«Ž$ýŽ:"A]¼Ÿ€\«Ýº‰‘îD’X3“yŒ“Ž”••`˜–tù–Dn—Z³—^˜Ÿm™¦ š3´šxèš<a›“žœŒ2Ê¿Šž$›ŸcÀŸ;$ •` ›ö ¿’¡R¢f⢨I£²ò£p¥¤Ú¥×ñ¥ÆÉ¦½§ŠN©“Ù©6mª¼¤ª‚a«Ý䫬XØ­11®]c®Á®}A¯`N¡°=ð²A.´Þp´—OµkçµNS·J¢¸í¸–¹D™¹3޹ߺÎòºHÁ»¤ ½‰¯½ 9¾‚F¿)É¿#óÀÂ\)Ä­†Äí4ÅW"Ç zÇP…ÈÖÈ êÉ¿÷Ê}·Ëo5Ìy¥ÌÍE;ÎIÎBËÎmÏh|ÏåÏ_ëÐ]KÒm©ÒnÓ‚†Óx Ô…‚Ô¬Õ¥µÕÝ[Ö·9×»ñ×Ö­Ø\„ÙøáÚbÚÛ¦=ÜôäÜ-ÙÝ Þ3ß EàrPá:Ããáþäàå7æ>8æ\wæÔæ½Tç[èrnèSáèi5éVŸé]öé.Tê8ƒêC¼ê.ë«/ë”ÛëÆpí+7î)cîbî+ðï»ð‚ØñL[ò&¨óIÏóõ{)õ¥õÃõvÛõåRö8÷1Q÷/ƒ÷0³÷Iä÷=.ø9lø¦ø'Æø,îø9ù+Uùù¡ù1²ùFäùF+úrú7úuÅú";ü%^ý„ýS£ý>÷ýL6þ=ƒþDÁþ+ÿZ2ÿ:ÿ<ÈÿI2O.‚h±4HO=˜EÖ=CZ3žeÒ;8tÝ… cZqÌ¥Ó 3y j­ ¥ ¨¾ §g P %` #† „ª É/gù‚aŽä sŠ}Dã`MD…’£8¼LõyBC¼•9–ÎÐCŸ@ãO$«t= =^Lœoé‹YfåL1θG¹V7X#>´ó~ ‹*¡Ì6ç 5!*S!~!™!‚®!$1"0V"‹‡"Q$ e%!'¤('Í'å'´(·)è¿*¨+‘Á+xS,$Ì,hñ,Z-«l-Ù.ò.©/.¬/-Û/9 00C0ct0qØ0‰J1VÔ1%+2JQ2Tœ2Áñ2³3 Ê3ë3v4z4¡4Ù25! 6Ž.7ͽ7T‹8à8÷9 ø9’:6¬:%ã:N ;X;çi;šQ<™ì<¤†=+>¹B>´ü>±?2È?Sû?ZO@!ª@Ì@-â@!AI2A'|A ¤Aº®A4iB…žCz$DŸD_¼DBE8_EʘEcFƒFŸF0¶FçF*G2GšPGÉëGxµH/.Ia^I ÀIáIþIpJ>ŒJUËJ3!K-UK¸ƒK\ã‰%"ŠJHŠ铊}‹ã—‹Þ{ŒšZ?õ(5Ž(^އޛŽ?¶ŽöŽ+1AGs5»%ñ9)Qs{#ï"‘6‘M‘h‘A‘ÑEß‘7%’A]’'Ÿ’5Ç’ý’3“(P“'y“4¡“EÖ“Q”-n”(œ”'Å”:í”P(•y•Œ‘•”–B³–7ö–B.—)q—×›—s˜‚˜”˜"´˜5ט ™*'™ R™Û`™?<š |š.†š&µš&Üš›é›dð›!UœRwœ4ÊœMÿœEM$“¸;ÐY ž+fž)’žS¼ž>ŸOŸ_ŸC|ŸÅÀŸ8† &¿ 5æ %¡)B¡}l¡,ê¡¢4-¢9b¢Aœ¢'Þ¢9£)@£$j£u£<¤JB¤ˆ¤¦¥4½¦«ò¦0ž§»Ï§Û‹¨¯gª¹°Ѱ.Ù±7³X@³k™³Š´´e°´eµw|µzôµ*o¶3š¶ ζ>ï¶4.·0c·;”·&з9÷·$1¸V¸$u¸Eš¸&ู#&¹#J¹#n¹1’¹%Ĺ)ê¹+º @ºKº%Zº€º-˜º,ƺ4óºA(»j»{»Ž»¥»·»ÂË»8޼Ǽå¼1½&4½[½x½Û‹½Dg¾ø¬¾\¥¿LÀpOÀèÀÀ©Á9Ây@ÃݺÄ€˜Å€ÆšÆd*džDŽȌ›È†(ɯÉU=Ê “ÊažË@ÌtAÍ\¶Í8ÎÎLÎ0Ï‚LÏQÏÏ›!ÐE½Ð:Ñ’>Ñ7ÑÓg Ô³qÔC%Õ5iÕŸÕo/ÖÏŸÖoo׃ß×¹cؘÙC¶Ù?úÙ„:Ú[¿Ú;ÛUWÛn­Û=Ü>ZÜf™ÜUÝ0VÝ~‡Þ7ß7>ß5v߬ßN:ૉàa5áL—áhäáëMâ 9ãÅDäo åXzå{ÓåeOæžµæÞTç?3èRsèÆè8Wé§é×8êºë<Ëëaì1jì<œìOÙìW)í=íX¿íDîž]î¦üî£ï­%ðˆÓðT\ñ±±ñacò)Åòïò ôx õ…õ@¡ö>âöÞ!÷YøyZøuÔø.JùByù¢¼ùk_úøËú3ÄûOøûDHü7ü…ÅüKýjOþrºþ-ÿ`­ÿE=T6’FÉu?†7ÆTþAS1•gÇT/E„DÊ 1K6k¢º¦ÆaX(%§ cE ~© i( â’ Åu Å;,I¼o {š^µ 05BfF©ðg hDrH·9²:Qíë?‘+¥½;cnŸZ!¶i!» "4Ü"ë# ý#$< %4]%3’%GÆ%+&:&C&"J&€m&0î&_(#)!£)¸Å)J~*eÉ*D/+ht,FÝ-7$/h\/Å/'Ø/?0@0T0Ê\0È'1Mð16>2#u3Ë™3re4Ø4Ü4!ã455Ê5 à6Îí6P¼7» 8´É8]~9çÜ9ÐÄ:+•;+Á;+í;†<. <'Ï<1÷<)=!<=+^=(Š=³=#¼=ëà=¼Ì> ‰@*”@,¿@8ì@ %A3A>GA^†ABåA/(B‚XBvÛBRCœdC1D!3D®UDÈE5ÍEFLF¸lF%H*H .H);HeH1~HQ°H7Ic:JežJK«K ÈLòÕL¸ÈNBOCÄOhP<qQ®QAµQô÷QìR$ûS¸ T±ÙT‹U`ªU5 WAWQW>aW W+¶WâWúWX+X=XTXjX‚X#œX ÀXÊX;ÜX Y„#YŨYGnZ$¶ZÛZ îZŽùZ§ˆ\0]:5] p] {]‡]Ž]¡]±] Î] Ú]Ôæ]\»^è_a~a˜b=)c8gdÿ d e¤ºeš_f>úf 9gËFgÛhZîhZIi¤i ÃiEÑi¶j¹Îj4ˆk½kÑkEák'l(0l‰Yl ãl.ñlO nFpn·o5ÆpŠüq¢‡s—*tBÂt“v™vÅ¢w€hxéx y(!yBJy¿yJMzý˜zB–{EÙ{"|B|™H|Bâ|Ë%~/ñ~!,89eŸ ¢$çè}€æ‚]õƒS„¦c…v †M†φOÖ‡b&ˆ ‰ˆšª‰™EŠ ߊyë‹ÔeŒ:˜AŽÄÚŽûŸŠ›g&‘”Ž‘/#’ S’@^’jŸ’â “„í“©r”I•Üf–C—U—³k˜™G2™uz™Lð™•=š¤Óššx›FœZœêœ {æ…lž·~ž|6Ÿ³Ÿ3 ><  { À‰ SJ¡-ž£äÌ£$±¤+֤ťŸÈ¥h¦ky¦L妟2§Ò§U×§G-¨mu¨wã¨#[©4ªª´ª_«'z«P¢«Àó«×´¬ŽŒ­¯¯L˯>°}W°ÌÕ°³¢±FV²{²n³5ˆ³A¾³=´…>´¾Äµƒ¶_¡· ¹+ ¹p9¹ ª¹ ´¹„Õ¹Z»_»g»%k»ö‘»nˆ¼“÷¼‹½¡½AÀ½ƒ¾œ†¾±#¿pÕÀTFÁ=›ÁuÙÁOÂNUÂ^¤ÂRÃVÄûZÄVÅjÅjrÅrÝÅ–PÆçÆðÆ4 ÇQ?È£‘È!5ÉWÉ\ÉdÉiɘpÉ Ê—Ê#¯Ê-ÓÊiË5kÌ1¡Ì3Ó̯ͷÍÃÉÍÀÏñNÐè@Ñë)ÒsÓ%‰Ó¼¯ÓlÔ{Ô„ŒÔÖž'Ö9ÆÖ8Ø*9ÙvdÙ1ÛÚÌ Û)ÚÛÜ Ü !Ü,ÜIÜ>gÜ¦ÜªÜ ²Ü¾Ü ÐÜCÜÝ] Þ~ß+–ß=Âß³à ´àsÂàl6âì£â/ã}Àã >äIä^äyä‚äpˆäùäp åB|åK¿åK æWæ,ræ*Ÿæ&Êæñæç`-ç Žç›ç³ç1Êçrüç·oè¢'é‘Êé[\ëu¸ì£.í5Òí’î*›î#ÆîêîðÿîÁðï=²ðÍððk¾ñ£*òÎòãò;øò74óÀló-ôÊAô& õ3ö-Cöqö£÷=¦÷=ä÷"ø¤7ø;Üø,ùEù Wù!eù‡ùù$•ù$ºùßùäù÷úû.&û=Uü§“üv;þ…²þ8»ÉH…±ÎZ€_Û;">ÅaO'w Ž £› À? Ö B× ï x _ƒ­ã1‘¶Ã[z†Öò]jP©»'e¿ÒP##ƒGŽËZtü„h‰êñtf ‚ ?Ÿ ß v_!)Ö!="/>"'n"(–")¿"8é""#~>#¦½#wd$´Ü$)‘%»%GÌ&2)`G).¨)Ð×)€¨*C)+vm+fä,9K-•…-z/+–/(Â/Õë0êÁ1¼¬2Ûi3WE5T5/ò5#"6"F6mi6(×6 7 8›9K¬9£ø9ªœ:QG;™<}©='>˜§>e@?w¦?~@S@!ñ@AN1A´€A_5Bq•BÌC²ÔC°‡Dù8E²2FøåGúÞH’ÙI«lJ:KÑSK&%L•LM âMAîN40OÅeOt+P] PþQ\R`RviS=àSQT=pT¬®TQ[U™­UnGV±¶VThW7½WuõWkX2†Y¹Y*JZ.uZk¤ZÛ\rì\D_]r¤]†^Ÿž^º>`Cù`=a†DaËalëaNXb §b3±bÝåbÃcÈc#äc/dn8d€§da(eŒŠeðfEgWNg¦g¿g+ÙgChÊIhjMjhjÂ…jHkEQkŸ—kÛ7l´m!ÈmÐêm<»nÜøoèÕqn¾rY-t ‡t•t/u>Eu„uP˜u.éw/xSHy†œyT#{sx{#ì{Ë}fÜ}éC~X-G†•ÎRd€2·€_ꀌJ~×V‚{eƒ|áƒ4^„Œ“„± …Ò…&ò…†)†A†F†!c†…†—†§† ¾†8ˆ2‡A7‡y‡•‡«‡Ƈ χ<Ù‡ˆ4ˆ =ˆKˆ3]ˆ‘ˆ¡ˆ&°ˆ#׈ ûˆ9‰B‰ Q‰[‰m‰t‰)’‰¼‰ ͉6Ù‰Š!Š5ŠJŠhŠ‚ŠŠ*³ŠÞŠýŠ‹1‹M‹`‹v‹‹¬‹¿‹È‹Ï‹4Õ‹ IŒ9ÖŽ.0Ž8_Ž˜Ž„¶ŽÔ;««¼ˆh‘Ýñ‘OÏ’~”ºž•\Y–L¶–w—w{—ó—ú™L švZšGÑš·›CÑ›=œ<SœBœÓœ4çœie†uìŸsb —Ö |n¡Jë¡è6¢d£$„£P©¤2ú¤¼-¥`ê¥EK¦q‘¦H§=L§wЧ:¨*=¨,h¨B•©YØ©y2ª@¬ª’íªŽ€« ¬5°­¯æ­|–¯"²<6³Is³½³==´N{´‘Ê´%\µ‚µA…·Ç·Û·Ïõ·%Ÿ¨ë¸˜”¹®-º§Üºw„»7ü»K4¼L€¼;ͼ# ½‰-½Q·½U ¾*_¾RоUÝÁë3ÂiÃÖ‰ÃJ`Ä3«ÄþßÄ)ÞÅRÆ[Æ9oÆž©ÆeHǦ®Ç-UÈAƒÊ1ÅÊH÷ÊE@Ëw†Ë’þËБÌ|bÎDßÎG$Ï-lÏWšÏ‰òÏ*|Ðd§Ðf ÑhsÑÁÜÑ)žÒÈÒÜÒ?\ÓÒœÓ4oÔ.¤ÔKÓÕ0Ö:PÖ©‹ÖB5×#x×Yœ× ö×Ù_+Ù?‹Ù!ËÙíÙU Ú°aÚBÜ„UÜ9ÚÜCÝ=XÝÑ–Ý…hÞ2îÞv!߃˜ßFà>cà`¢àgá»káh'âõâe†ãGìã‹4ä?ÀäTåMUå{£åtæ/”æ%ÄæêæÒ çÝç%ñç¼é±Ôé>†ëOÅëìA¥ìCçìH+í&tíb›í=þíG<îY„î)Þî4ïS=ï7‘ï2ÉïÈüï:Åðñzòx‘óŸ ôNªôOùôbIõK¬õÔøõ®Íö³|÷0ùDùnZù/ÉùlùùyfúúàúÛüvãþ—ZÿEò¥8kÞJJ•+¯íÛÉêKD6|{Gø@UV¬QËÄ ]â A@ H‚ ŠË NV ?¥ *å ª » EÛ !! +CoÑ…OW7§Jß*˜<´ÕBŠUÍ#u%:›oÖwF6¾´õšªOEè•3~<²[ï#Kˆoø;xPwÉIA‹[“ï=E3Å„ùR~ õÑ )Ç!Nñ"J@#a‹#‘í#â%2b&•&¯­'G](Ð¥(v)wŒ)/*4*AJ*æŒ*)s+$+QÂ+L,ra,mÔ, B-P.Hà.¨)/;Ò/G05V0(Œ03µ06é0' 1H1*[1*†1(±1(Ú1*2.252-Q22&™2À24Ü23"*3M3 e3 o3 z3†3•3¦3Ä3Ö3ð344614.h4(—4.À45ï43%5:Y5”5¤5#À5ä5#61$6HV6+Ÿ6Ë6Ü6ï676(7"_7!‚7*¤72Ï708038.d8“82™8Ì8Õ8 î8ù89-9<9O9d9v9‘9.¬9Û9ó9-ü9+*:V:&g:Ž:®:"Ã:æ:ý:6;O;o;"Œ;*¯;Ú;ò; <%!<G<)\<Y†<à<!÷< =#=A=[={= –=%·=Ý=ú= >Ó->?3?O?m?Œ?2¨?Û?#ø?-@ J@W@v@*‘@ ¼@Æ@1Õ@$A&,A1SA#…A©A#ÅAéA B, B(9B=bB! BÂBÛBIðBj:C1¥C+×CDD(D=DSDSZD®D²DÁDÚD4îD3#E WEdE‚E# E#ÄE'èE%F&6F9]F—F;¯F#ëF&G6GMG]GwG G>G[ÜG 8H.FHuHŒH©HÁH4ØH" I0IAIRI fJ ‡J ’JžJ<¹J;öJ<2K;oK «K¸K ÒKÞKýK9L(KL(tLL´L!ÏL›ñLlM.úMe)NƒNGOÁ[O^RY|RdÖR:;S;vT4²TÁçTA©W@ëX¥,YDÒYXZIpZ¦ºZAa[£['¬[Ô[ò[[\!m\\'¨\Ð\î\÷\(ý\&]@]U]1j]œ]5¸]-î]?^"\^!^%¡^=Ç^_&$_*K_=v_$´_Ù_ð_3`"6` Y`,z`;§`%ã` a&*a#Qa'ua&a/Äa*ôa b@b!`b‚b›b·bIÏb?cYc+vc2¢c1Õc$d9,d'fd Žd-¯d&Ýd'e,e Ke"lee)¯e&Ùe,f,-f!Zf'|f&¤f:Ëf&g!-g&Ogvg#’g,¶g-ãg#h!5h(Wh"€h£h¿h$Þh6i':i/bi(’i!»i Ýi þi1jQj#mj)‘j»jÚj*ïj!k/H}‡}œ}¼}Ü}ú}~#%~I~]~z~-‘~¿~Õ~í~JPnuެÆ! )"€,L€"y€œ€µ€Ï€ë€%% KVk†7ž<Ö0‚6D‚9{‚8µ‚4î‚9#ƒI]ƒ&§ƒ3΃„ !„4/„d„+}„5©„#ß„ ……*…@…S…h………!—…¹…Ì…æ…(þ…)'†NQ†4 †IÕ†‡9‡Y‡m‡‡'Ÿ‡LJâ‡ü‡ ˆ$9ˆ)^ˆˆˆ7§ˆ,߈ ‰4‰6N‰+…‰/±‰)á‰( Š*4Š(_Š-ˆŠ'¶Š ÞŠëŠ# ‹ -‹8‹M‹\‹v‹8…‹¾‹1Ò‹ŒŒ)Œ1ŒCŒ3_Œ%“Œ¹Œ)ÖŒ&"Dg0†)·áŽpŽŽ©Ž1ÅŽ"÷Ž7R j"‹+®/Ú 0P.c’6±%è‘'‘8‘ P‘[‘ˆm‘ö‘ ’5#’$Y’ ~’0Œ’3½’"ñ’>“CS“5—“Í“4Ý“ ”,3”`”|”•”!µ”×”+î”*•5E•({•(¤•6Í•"–€'– ¨–µ—Í—<Ý—˜Qœ˜î˜™#!™"E™h™‚™"”™·™ ¿™à™û™š$!š!Fš.hš—š²š Éš,ך&›!+›M›m›‹›¦›!Á›$ã›,œ5œ Qœ_œ)zœ¤œÀœÜœ3ûœ(/6X#³ Ï Ù9ú%4ž]Zž¸žמ%ꞟ%ŸCŸ'`Ÿ8ˆŸ&ÁŸèŸþŸ 6 V ,r Ÿ $µ  Ú æ #ï ¡+3¡Q_¡E±¡ ÷¡'¢!-¢/O¢¢,ž¢"Ë¢)î¢B£"[£~£)‘£»£>Ó£/¤B¤,b¤¤7•¤'ͤ'õ¤¥6¥F¥4V¥‹¥#¦¥!Ê¥ ì¥3 ¦ A¦M¦`¦|¦“¦ ¤¦&Ŧì¦/§"4§W§)u§aŸ§¨5¨->¨0l¨¨#²¨Ö¨)ê¨!© 6©#B©f©{©Ž©¨©·©Щè©"ü©ª*3ª?^ªžª­ªȪAáª#«B«&\«!ƒ«¥«&»«(â« ¬&¬+=¬0i¬&š¬LÁ¬­+­C­b­{­’­«­¿­Ó­'î­0®G®"Y®|®,“®-À®)0¯(F¯ o¯&¯·¯Ó¯ ê¯÷¯°&,°S°j°‰°›°¯°2ϰ±&±A±J±e±ƒ±£±¼±Ô±é±#²*²5?²&u²1œ²β!ä²'³.³E³-c³‘³ –³#·³Û³"ó³´2´B´X´j´‚´¡´(¹´â´4ý´82µ3kµŸµ¥µ‰ÀµJ¶"h¶‹¶!ª¶,̶ ù¶ ··+,· X·f·„· ·¾·(Þ·)¸+1¸]¸=y¸ ·¸Wظ0¹-L¹Cz¹8¾¹2÷¹ *º$Kº(pº!™º»ºÚº÷º»8» T» _».k» š»D¥» ê»+ô» ¼(-¼)V¼)€¼-ª¼ؼç¼½½*½D½$[½€½›½'»½"ã½)¾+0¾\¾&k¾’¾ ®¾º¾̾Û¾ ÷¾¿¿,.¿-[¿8‰¿¿Ñ¿Ö¿æ¿ÀÀ"À 4ÀAÀYÀ pÀ‘À!©À*ËÀöÀ Á )Á7ÁKÁ-cÁ*‘Á¼ÁÔÁ8ÛÁ7ÂLÂg ƒÂŽÂ#¦ÂÊÂ3æÂ Ã-$Ã#RÃvÕóÃÅÃÙà ðÃ.Ä+@Ä!lÄ ŽÄ!¯Ä#ÑÄõÄ Å*Å#HÅ lÅŨÅÇÅ/àÅÆ8+ÆdÆ>wÆ ¶Æ0ÄÆ õÆ!Ç %Ç03Ç&dÇ=‹ÇÉÇäÇ5þÇ!4ÈVÈ gÈtȔȩÈÉÈéÈùÈÉ,ÉCKÉɦÉ4ÁÉöÉ&þÉ%Ê@ÊUÊoʇ‹Ê4ËHÌ]ÌwÌCŠÌ!ÎÌðÌùÌ$Í/3Í&cÍ;ŠÍ)ÆÍ'ðÍ3Î*LÎ wÎ!˜Î"ºÎ#ÝÎ)Ï+Ï=ÏMÏbÏ{Ï4›Ï!ÐÏ}òÏ*pÐ$›ÐÀÐ+ÚÐ#Ñ(*ÑSÑ'jђњѰÑÊÑ åÑ,òÑ,ÒLÒ2fÒ!™Ò!»ÒÝÒ,ñÒ(Ó:GÓ ‚Ó4Ó>ÅÓ$Ô )ÔJÔ=iÔ'§Ô ÏÔðÔÕ 'Õ 2Õ SÕœtÕÖ))Ö*SÖ/~Ö®Ö(ÅÖ)îÖ!×':×b×x×'–×5¾×(ôר':ØbØ!‚ؤØÄØOàØ40Ù$eÙ ŠÙ&«Ù'ÒÙ úÙÚ$Ú CÚQÚgÚyÚ:ŽÚCÉÚ+ Û!9Û[Û,sÛ Û±ÛÏÛíÛÜ!Ü>Ü]Ü-lܚܰÜ.ÈÜ÷ÜÝ+ÝEÝeÝuÝ.ŽÝ9½Ý÷ÝÞ'Þ+FÞrÞ8‰ÞÂÞÖÞ òÞ"ß'#ß-Kß)yß1£ß#Õß.ùß (à!Ià8kà¤à§à¿àÚàóàá á:áNáWásáhá8ùá62â4iâ$žâ$Ãâùèâ/âä!å4å,Råå)ŸåÉå"ßåæ&æ)Eæ9oæ©æ Àæáæ!øæ%ç"@çcç€ç3œçÐç'Øçèè9èUèjèˆèšè¹èØèíè!é&é$Eéjé}é›é"­éÐéãé-ôé"ê;ê,Xê…ê#™êj½ê(ë$¸ëÝë&úë4!ì#VìzìŠì$ì>Âì1í3íMídí|íYí%êíî)îÐ<î( ï36ïjï"Šï?­ï íïð$"ðGðað@}ð¾ðØð&õð ñ&ñ?ñXñuñˆñ(œñÅñÜñ9õñ7/ò&gò Žò1›òÍò íò-÷ò %ó(2ó%[ó?óÁóßóøó,ô ?ôKôdôxô7ŒôÄôßô+úô&õ9Eõ-õ'­õÕõ+æõ ö+3ö_ö~ö+•öÁö Üöêö÷ ÷9<÷!v÷,˜÷6Å÷ü÷% ø)3ø]ø,sø  ø¬ø(ÃøìøH ùTRùT§ù0üù!-ú Oúpú#ú"´ú#×úûú"û*1û3\û6û>Çû#ü*ü$Hü!müü"«üÎüÞüõü5ýFý@Yý!šý¼ý/Ïýÿýþ -þNþaþuþ!‡þ$©þ ÎþÙþ"ñþÿ*&ÿ$QÿvÿŽÿªÿ0¼ÿ4íÿ";QDj¯Ä#Ùý 4<OqÁÞ÷"!+Mm€‘«%Âèþ  'M2M€Îá#÷)#CM‘§¹Ïâö +Kau+•ÁÙ$ø"4Wi%„ªÈ'å9 "Gj˜#©7Í>D_&y µ/Ð ' @ R i  ’  £ ° Î  ß  í   $ (0 [Y Lµ C +F <r #¯ #Ó "÷ - 6H * ª !» 2Ý 5 4F +{ 9§ <á 3(R{4ŒÁÓäöG 6Q%ˆV®A GjhWÓV+Ê‚_M™­VGWžOö_F–¦2=8p9©[ã*?1jœ  ¬!³=Õ"A63x¬È.á&7T1i0›=Ì" -E.eE”3Ú)/8%hŽ<®ë -;W5u*«'Ö$þs#—2Ÿ6Ò Oro—â#z"ž"Á(ä- <; (x #¡ Å ß û !9!5X!Ž!ª!"Ã!"æ!8 "3B"0v"%§"Í"#ì")#4:#)o#7™#Ñ#à#Iè#+2$W^$!¶$Ø$ì$ %%/%G%-`%&Ž%µ%È%à%ù%&/&K&d&"}& &0¶&*ç&%'8'.W'!†'$¨'Í'#ä'((.-("\("(#¢($Æ('ë()1)K) _)€)0Ÿ) Ð))Ü)*%*:D*$* ¤* Å*4æ*+#++)O+y+ “+Ÿ+&¸+?ß+!,A,&],/„,0´, å, -'-:.-i-ˆ--¨-(Ö- ÿ- .!<.^.-y.(§./Ð.$/%/A/"Q/t/‘/2ª/#Ý/)0-+0!Y0!{050&Ó0&ú0,!1N1'V1~1˜10´1Hå1C.2&r2™2E¯2#õ223"L3o3€3™3µ3 Í3Ù3)ñ304%L4/r43¢4 Ö4"÷45 05=5.M5%|5#¢5,Æ58ó5",6O6i6x6&‹6²6&Ã64ê6*7&J7q7‘7°7(Æ7 ï7N8_8 g8u88&®8Õ8*ó8949L9f9w9‰9 ™9¤9Â9É9FÙ9 :,2:=_::°:#Ê:.î:;'4;#\;8€;.¹;è; ñ;þ; <##<"G<#j<#Ž<'²<)Ú<=!=+A=&m=$”=(¹=&â= >7%>+]>-‰>·> Ô>$Þ>1?/5?;e?'¡?!É? ë?õ? @'&@N@n@0Œ@"½@!à@?A,BA0oA! AÂA(ÞAwBwB+÷B0#C&TC{C „CC¢C'µC0ÝC'D 6D(CDlD‡D.¡D-ÐD þD E&$EKE fE#sE—E¶EÍEßE÷E F$F3F)GF+qFF °F ÑF-òF G;GNG bGpGGªGÂGßG-øG&H>HdVH:»H%öH8I4UI8ŠI!ÃI-åI+J?JWJ:wJ²J'ÅJ%íJ/K1CKuK‘K¦K1¸K%êK&L87LpL†L=ŸL)ÝL(M0MEM[M#uM*™M1ÄM)öM N ANON1eN—Nš N";O$^OƒO¢O½O#ØO*üO/'P$WPe|P*âP Q *Q&KQrQ†Q˜QªQ¾QÕQ&çQR%R%5R [ReRR•R¨R.¾R0íRS :S)HSrS ‹S$˜SϽSBT$ÐT7õT-U(AU)jU;”U%ÐU!öUV;5V!qV“V±V(ÑV*úV,%W?RW*’W,½WêW$X (X4X"IXlX)†X°XËX1êX5Y%RY*xY"£YÆY&áY#Z,Z5ZDZXZ8_Z%˜Z ¾Z'ÈZ ðZ[([D[)`[,Š[·[8Ñ[ \%\&B\ i\/Š\º\Ø\Eõ\I;]J…]£Ð]9t^®^-Ê^/ø^-(_V_o_"‹_-®_Ü_ä_í_$ÿ_$`&@`"g`'Š`#²`5Ö`" a/aLajaˆa+¨a^Ôa$3bXb#xb"œb¿bØb5öb1,c9^c:˜cßÓc%³dÙdèd,e+3e$_e'„e'¬e)Ôe$þe#f>fOf ^fjf+|f0¨f,Ùf-g'4g1\gŽg+ g"Ìgïg+ h"9h\h.th"£h&Æh(íhi#1iUi#ni’i²i8Èi?j%Ajgj1‡j¹jÕjój k)kBkYkqk%‹k%±k×k&îk l7 l3Xl!Œl®lÊl ãl<íl*mBCm†m%œm$Âm"çm n'n$Cn%hn$Žn³nÂn$Þn"o&o;Bo ~oŒo£o«o´o!Ño%óo!pF;pK‚pAÎp!q2q%Qq&wqžq#¼q3àq'r*gr+¦rÒr$Ùrþr"s5s Ps/\sŒs¬s!Ês+ìst/t)Ct mt,yt¦t+¹tåt,õt"u5uSu8nu_§u%v-v-MvX{vÔvêv ùvw6w+Vw ‚w£w¼wÙw%ßw!x6'x5^x”x/«x>Ûx3y"Ny+qy1yNÏy6zUzjz†z"¥z Èz0éz {%{&;{&b{‰{*¤{ Ï{"ð{|@|!]|||w®|.&}"U}x}(“}>¼}û}~ 2~8?~/x~¨~1Ä~0ö~+')S}•²/Îþ€5€E€e€t€8‰€€Ø€)õ€L)l&–$½Eâ?(‚h‚~‚–‚°‚%Í‚&ó‚5ƒPƒ&lƒ“ƒªƒvă-;„)i„+“„¿„IÖ„ …6…4V…%‹…6±…è…C†UK†¡‡&§‡#·ò‡ˆ.#ˆRˆoˆŽˆ¦ˆ7È ûˆ>‰E‰^‰(r‰›‰)»‰å‰ü‰ŠI3Š}Š•Š"°Š5ÓŠ ‹#‹"C‹f‹#…‹©‹Ç‹,æ‹!Œ45ŒejŒÐŒ2ïŒ!" DewŠ¡*¿Pê;Ž5OŽR…ŽØŽ6êŽ,![N%ª&Ð÷$+B,\‰¨Ä!ÜþK‘'f‘(Ž‘·‘&Ì‘ó‘ ’ ’(’F’_’s’’¤’)¸’â’ú’“0“!C“e““™“¬“ēړö“””5”E”Y”i”‡”–”°”Ê”#ß”••7•Q•e•{•#™•½•Õ•#ð•– %– F–S–%j–-–¾–FÕ–@—$]—2‚—µ—Ó—Ü—ù—˜.˜F˜f˜"€˜#£˜!ǘ#é˜ ™*™-?™m™™¡™Lª™÷™0šGš,\š ‰šªšÉšÜš6õš8,›.e›#”›3¸›ì›ÿ›œœ:œYœoœœ ¡œœÜœëœ"þœ!A$Y~•A±%óž.ž@Mž$Žž-³ž+áž% Ÿ13Ÿ5eŸ›Ÿ8¯Ÿ1èŸ, 1G Ry Ì 6ì 5#¡Y¡#q¡2•¡1È¡'ú¡'"¢,J¢w¢—¢:µ¢"ð¢'£&;£#b£†£–£8³£$ì£ ¤-¤!J¤l¤ ‹¤¬¤;¾¤ú¤)¥&A¥h¥¥–¥/®¥)Þ¥"¦%+¦Q¦#d¦ˆ¦£¦&¾¦,å¦)§#<§!`§)‚§¬§§ á§ë§ñ§ ú§@¨E¨\¨3p¨4¤¨@Ù¨4©3O©ƒ©5›©&Ñ©4ø©&-ª"Tª5wª ­ª7ºªòª«( «!I«5k«¡«BÀ«"¬"&¬=I¬3‡¬-»¬8é¬Q"­2t­A§­Jé­‰4®¾®1@¯rr¯*å¯&°A7°(y°=¢°;à°-±\J±L§±@ô±25²,h²a•²6÷².³9M³)‡³5±³!ç³* ´44´.i´+˜´6Ä´(û´3$µ0Xµ‰µ¡µg¶µw¶#–¶"º¶9ݶ2·3J·H~·RÇ·'¸çB¸r*¹+¹eɹK/º5{º@±ºòº+» <»#]»"»*¤»;Ï»( ¼#4¼-X¼+†¼3²¼æ¼5þ¼&4½([½1„½3¶½ê½ò½/¾A¾]¾ w¾'¾©¾ȾÛ¾2iÀ,œÀ3ÉÀ3ýÀ?1ÁBqÁ7´Á7ìÁ$Â@@ÂTÂÖÂõÂ8Ã8KÃD„Ã8ÉÃ<Ä>?Ä0~Ä(¯Ä>ØÄHÅ`Å}ŘÅG­Å-õÅ2#Æ\VÆX³ÆJ Ç/WÇ4‡Ç ¼Ç2ÉÇüÇÈ;ȉYÈÓãÈF·É?þÉ>ÊYÊlʇʚʹÊ*ÐÊûÊË3ËBË SË tËË$™Ë¾Ë-ÐËþË1 ÌO?ÌÌÍ”ÌObÍ|²Î°/РàÐÑŸÑœ½Ñ ZÒœûÒi˜ÓÔR‚ÔRÕÔ£(ÕŒÌÕYÖ+o×-›×É×ã×Sþ×:RØ4ØÂØ‰ÞØ8hÙE¡ÙçÙÚ"!ÚDÚcÚ5Ú0·Ú9èÚ@"Û,cÛ:Û+ËÛ,÷Û)$Ü-NÜ'|Ü+¤ÜµÐ܆Ý2žÝ4ÑÝ)Þ!0Þ$RÞ)wÞ!¡ÞÃÞÜÞ.ñÞ$ ß/Eßuß#‹ß¯ß=Éßà1àAOà.‘à9ÀàJúà)EáGoá2·áêá-â02âcâ+â!­â Ïâ1ðâ"ã<ãUã3iã,ãÊã.æã%ä$;ä#`äF„ä'Ëä+óäå3å3Gå0{å-¬å?Úå)æ*DæoæŽæ§æÇæ9ßæîç‚è‘‹è’郰éµ4êYêêLDë«‘ë=ìýNìåLí·2îÛêî(Æïïï”ð†¤ð÷+ñó#òÇó¿ßôQŸöfñö Xø7døŠœùú'ûØ"üÔûü\ÐýÀ-þjîþ Y Cc ®§ ¸V ß Jï C: @~ W¿ ? DW ‰œ G& vn Kå ^1 O ^à b? =¢ Jà (+ LT Z¡ :ü O7 W‡ Lß =, ^j \É =& Žd Gó F; C‚ 4Æ bû C^ W¢ =ú O8 Oˆ OØ U( R~ dÑ U6 WŒ \ä LA CŽ 7Ò D  @O + 7¼ Zô CO ]“ Fñ ^8 H— =à M 1l 8ž F× F ¢e » YÄ B Wa ^¹ ] ]v 8Ô I FW bž a! Sc! R·! “ " dž" a# 7e# +# OÉ# Z$ _t$ UÔ$ _*% CŠ% LÎ% \& x& U ' <_' !œ' 5¾( Vô( TK+ ç + °ˆ, Œ9- …Æ-  L. ôí. `â/ C1 /]1 1 ¢2 ¨¿2 Õh4 >6 I6 ²T8 ý9 ß: ßå:  Å; wf< ˆÞ= jg> XÒ> +? Æ6? Iý? G@ ×@ gA rC ~D ŽE ,H LI PTL ©¥L =OM YM )çN 8P JQ 5ZR ?R =ÐR S 7&S <^S ›S 3)T w]T =ÕT ØU (ìU V 3V TV !tV œ–V I3W 8}W ¶Y S8[ ,Œ[ ê¹[ ]¤\ Ÿ] @¢] ¥ã^ }‰_ Ä` Ì` vja áa b k b 3Œc ®Àc ðoe Ã`f Ú$g îÿi ´îj ^£k Ïl ¡Òl ?tn ï´n äo 'hp Ir RÚs (-t :Vt R‘t +ät (u R9u ¦Œu õ3v K)w ½uw »3x Áïx ¨±y ¢Z{ ý{ ñ} D~ ïE %5 e[ƒ ³Á„ Ku… JÁ† m ˆ _z‰ •ÚŠ ép …ZŽ àŽ [ R\ ¸¯‘ rh’ ‰Û’ e“ ÷å“ ¾Ý” |œ• †– z – s— l— kü— h˜ ú|™ +wš &£š Êš #èš  › ¥œ V¾œ V l i}ž ‚çŸ j  Éo¡ 19¢ ]k¢ UÉ¢ F£ ¨f£ 3¤ C¥ ÿ\§ \\© ª¹© ¾dª 9#« ´]¬ ­ @1® ¬r¯ –± ¸¶² \oµ B̵ '¶ ¢7¸ ‘Ú¹ ¨l» H½ å^¾ D¿ ƒFÀ `ÊÁ +à ­¼Ã ýjÄ hÅ vÆ 4†Ç [»Ç lË S„Ë §ØË £€Ì Y$Í e~Î äÏ höÏ V_Ñ L¶Ó MÔ ÷QÔ ¹IÖ õ× 9ù× ª3Ø gÞØ @FÚ 6‡Û ;¾Ü :úÜ ª5Ý àÝ AïÝ 51Þ >gÞ ,¦Þ ;ÓÞ 5ß /Eß ^uß NÔß C#à .gà E–à 1Üà Ká Zá ¯dá ¼â ˆÑâ ˆZä Tãå ®8æ Èçæ ò°ç ‘£è –5é WÌé a$ê †ê kì 4‚ì k·ì ù#í †ï W¤ï Ìüï [Éð U%ñ |{ó døô 5]õ €“ö ÷÷   ø Ä­ø Ùrù ²Lú  ÿú  û V>ü ž•ý •4þ gÊþ ©2ÿ ÂÜÿ ëŸ !‹ ˜­ F ôÖ ðË ƒ¼ ý@ Ó> “ ¸¦ Ž_ 0î  í7 n% e” bú }] ¡Û }  ‹+ ¥· ?] ù a— cù ³] á Åó ‹¹ ŽE ]Ô C2 Äv! &;" Çb# ø*$ Œ#% )°% ‰Ú' ¯d) * 3+ iT- _¾/ ›1 „º1 µ?2 ¥õ2 x›4 G5 À\5 J6 °h6 Â7 ¢Ü7 8 Ÿ9 Á½9 Ÿ: {; Ó›< øo> dh? Í? ŠÏ@ ZA !{B XC ;öC @2D  sD ÝE PòF MCH f‘I øI JK ³cK .N ‘FN ^ØN 7O IÅP lQ Q|R ÎR ±ÖS ²ˆT P;U óŒU Z€V ýÛV éÙX ÃY aZ ¢ÿZ Ÿ¢[ žB\ >á\ ê ] » _ ªÇ_ Žr` Sa ×Ua ü-b R*c É}c Ge ”df Ãùf g½g [%i Oi ÑÑi ˜£j ä{ ª { ŸK| aë| fM} Û´} a~ 4ò~ 9' 9a 9› 0Õ Z€ Fa€ b¨€ › …§ \-‚ SŠ‚ XÞ‚ Y7ƒ `‘ƒ Ròƒ ŒE„ hÒ„ Z;… —–… f.† Y•† wï† g‡ Ilˆ <¶ˆ •óˆ W‰‰ UበZ7Š L’Š xß‹ XŒ V_ +¶ 1â :Ž OŽ ‘l ¾þ ú½ m¸‘ _&’ 7†’ ^¾’ (“ .F“ (u“ .ž“ %Í“ ó“ %” +6” )b” FŒ• ^Ó• ï2˜ Ÿ"™ ²Â™ Âuš ™8œ £Òœ £v ;ž ‹VŸ h⟠iK  Sµ  Ô ¢ |Þ¢ B[¤ ƒž¤ J"¨ ¦m© zª p« ­ ° ± ~&² ˜¥³ >´ LS¶ K ¶ ì¶ fô· O[¸ Q«¸ Ký¸ JI¹ •”¹ ³*º NÞº K-¾ ay¾ aÛ¾ a=¿ JŸ¿ Gê¿ (2À ¡[Á ±ýÁ S¯Â ÈÄ €ÌÅ <MÇ ŠÇ Y˜È ¯òÈ —¢É ð:Ê r+Ë ÅžÌ ÈdÍ R-Î <€Î 2½Î RðÎ RCÏ 9–Ï ŒÐÏ ¯]Ð p Ñ #~Ó º¢Ó v]Ô šÔÕ ïoÖ _× !ï× bÙ µtÛ ·*Ü ÇâÜ ?ªÞ ÉêÞ Ú´ß :á ÂÊâ Wã ÿåã åä ²õå Æ¨æ Éoç S9ê Tê íâê YÐë Š*ì ³µì Xií RÂí eð þ{ð ”zñ ÷ò `ó Âhô É+õ Éõõ Ÿ¿ö €_ø /àù û ³žû ŸRü Hòü »;ý ;÷ý F3þ Nz ®É &x `Ÿ Î ÁÏ ‡‘ = LW N¤ Gó ‚; ·¾ v Dy ’¾ ¹Q µ nÁ ”0 ¯Å Zu –Ð òg ÈZ Ë# ?ï y/ © ¾² Âq ü4 ¼1 <î ƒ+ m¯ ö ò  Æ dà ÷E! ²=" ð# Zp$ ÈË% Ï”& Kd' ë°) ©œ* ’F+ YÙ+ Å3- ù- r / Š}0 E1 zN1 ŒÉ1 ŒV2 ÿã2 ã3 àç6 €È8 *I9 ¿t: c4; ¦˜< \?> œ> ´> fw? 7Þ? ù@ $A Õ5B  D éE €ÿE ~€G :ÿG ::I ÂuJ ‚8M )»M ÿåN ƒåQ ›iR [T aT P~U àÏV ©°W ZX ÅwY f=Z e¤[ V \ ia\ °Ë\ ¡|] Æ^ âå_ †Èa ´Ob ™c Äžc œcd  e Í¡e of zg ç|h ëdi þPj ŠOk `Úl –;p Òp Qíq -?s ms 3wt «u Ͷv s„y áøz Ú{ 7ú{ >2| xq| Ãê| ½®} [l~ ‚È~ hK i´ V€ ]u€ .Ó€ 8 C; . «® MZ‚ Z¨„ B† 7F† R~† 6ч ш §Ú‰ ‚Š 4Œ jEŒ ° {¿ 1;Ž mŽ v…Ž üŽ Œ 1¥ /× 0‘ I8‘ =‚‘ 9À‘ ú‘ '’ ,B’ 9o’ +©’ Õ’ õ’ 1“ j8“ j£“ ” C)” 4m” &¢– *ɘ ô˜ S™ >g™ L¦™ =ó™ D1š +vš Z¢š :ýš <8› Iu› 2¿› .ò› h!œ 4Šœ H¿œ = EF =Œ CÊ 3ž `Bž ;£ž }ß  õ]¢ GS£ ›¤ €+¥ Ǭ¦ Kt§ ’À§ ­S¨ ©© «© ’¿ª @R« >“« ÞÒ« '±¬ ¡Ù­ ¬{® ß(¯ C° ±L² þ² D³ bV³ k¹´ Æ%µ Öìµ Pö h· }· B ¸ žN¸ >í¸ ƒ,¹ X°º [ » fe» ÇÌ» X”¼ Ní¼ k<½ h¨½ x¾ qо –ü¾ ;“¿ Ï¿ †îÀ Uu FË Fà NYà ¨Ã —Áà YÄ FoÄ ¶Ä 6ÑÄ ZÅ cÆ ?Æ 9ÁÆ ûÆ •Ç $¦Ç 0ËÇ üÇ È Ê ,ÒË !ÿÍ ¤!Î ÆÎ ÞÎ ²ûÎ ®Ð ÁÑ ÇÒ °ÝÒ ²ŽÓ AÔ §bÔ ' Õ Õ2Õ íÖ %öÖ × F Ø EgØ X­Ø HÙ ÑOÙ D!Ú fÛ €nÜ FïÜ a6Ý {˜Ý 0Þ Eß \ß {ß ‘ß ¦à Õ¼à ‚’á §ã ³½ä -qå TŸæ ôæ ÷ç è Ÿ-è =Íè % é N1é €é þ‘é šê é+ë »ì Ñì ëèì ßÔí ´î 2Ëî Zþî ZYï !´ï Öï -ìï !ð S<ð 'ð ¸ð ÙÂð =œñ ŒÚò gó éó _ô Bfô 8©ô ûâô Þõ þõ ö 01ö bö *‚ö ­ö šËö ãf÷ xJø /Ãø aóø Uù vù “ù ²°ù >cú U¢ú 3øú -,û ¸Zû \ü Epü X¶ü ¼ý ÂÌý hþ Èøÿ Á \à r= ®° ,_ Œ m§  " 9 ?G w‡ ýÿ ý  ž4 íÓ šÁ ä\ A lX yÅ L? eŒ Tò 5G ?} J½  / $G Bl A¯ @ñ 72 j @€ Á Ï ß ï   " *5 ` p 6† ½ Ê é ÿ  + F> … à †~ © =¯ Yí @G ±ˆ T: Q ìá ,Î û " œ8 ¶Õ Œ ª ° п A wÒ UJ U  Ðö Ç ØÓ ç¬ Ó” 2h I› å 5î 8$! 2]! V! 5ç! n" Œ# ÙŽ$ !h% PŠ% JÛ% /&& /V& †& Ž& –& ž& ­& ¶& ¾& Æ& Î& Ý& ì& õ&  ' ' ' "' 1' @' I' ^' m' |' …' š' ¢' ¬' Á' Ü' æ' ,ÿ' ,( 4B( w( (—( À( Ù( ò( -) X=) R–) é) #* +$* !P* 5r* /¨* /Ø* 5+ >+ [+ Jt+ "¿+ %â+ ], f, y, ’, «, (Ä, í,  - '- @- !Y- {- š- ª- º- Ç- Ô- )á- % . @1. Ar. *´. *ß. 9 / XD/ / < / ?Ý/ 0 &20 :Y0 7”0 #Ì0 4ð0 %1 =1 "K1 .n1 1 "³1 AÖ1 (2 IA2 J‹2 0Ö2 3 33 2S3 5†3 4¼3 /ñ3 .!4 6P4 R‡4 1Ú4 4 5 RA5 ”5 9£5 Ý5 Mþ5 L6 \6 Ms6 5Á6 K÷6 ;C7 /7 H¯7 Bø7 B;8 ~8 G˜8 .à8 D9 DT9 4™9 <Î9 ? : 3K: 9: 0¹: ê: 2; *:; 0e; –; 3®; Fâ; `)< CŠ< JÎ< != ';= Bc= &¦= "Í= #ð= E> &Z> Z> 8Ü> ? )3? ]? 5u? D«? 9ð? ;*@ 9f@ R @ %ó@ #A /=A mA c‡A HëA ;4B )pB šB µB ,ÖB 1C 5C VC 1vC >¨C :çC B"D MeD ³D 8ÐD ? E >IE GˆE 0ÐE MF ;OF >‹F >ÊF S G A]G 8ŸG SØG Q,H b~H >áH " I 1CI "uI M˜I \æI /CJ ŒsJ &K *'K )RK 3|K 2°K @ãK ^$L SƒL M×L )%M OM AdM 3¦M EÚM e N >†N UÅN WO sO yO ‹O •—O -P f?P 1¦Q ÞØQ 4·R 2ìR ,S `LS Z­S ™T ¢T #³U é×U ÍÁV ÍW N]X L¬X KùX EY bY aY -áY @Z TPZ M¥Z 4óZ 9([ 6b[ ;™[ ¼Õ[ A’\ @Ô\ 4] -J] x] \–] *ó] U^ St^ _È^ :(_ Ic_ &­_ GÔ_ '` ED` /Š` Dº` Iÿ` 4Ia 1~a A°a @òa 3b &³b ™Úb ¥tc Td Fod K¶d 6e 9e ?f Uf $nf E“f WÙf 1g =Kg ‰g j—g ci fi Epi '¶i 7Þi j øj lk (k c¨k W l ~dl Zãl ->m lm Hˆm eÑm X7n Vn çn ]uo Óo +ío 1p Kp @lq (­q FÖq 9r 6Wr ºŽr :Is =„s 9Âs 4üs T1t U†t =Üt 'u %Bu Žhu <÷u I4v ~v þv ?y ñQy 2Cz õvz Pl{ v½} î4„ º#… Þ† ]ëˆ ‹I‰ zÕ‰ ƒPŠ ?ÔŠ Q‹ mf‹ tÔ‹ ŠIŒ ?ÔŒ 9 <N U‹ :á :Ž DWŽ .œŽ MËŽ 8 ;R -Ž W¼ / 9D +~ +ª +Ö ;‘ ;>‘ 2z‘ ,­‘ Ú‘ å‘ Iô‘ >’ -V’ ,„’ 4±’ Aæ’ (“ 9“ L“ c“ u“ ‰“ SL” 7 ” 1Ø” 4 • <?• 4|• '±• Ù• Ví– aD— ƒ¦˜ T*™ °™ 0š ŸL› 2ì› · ;מ x  yŒ  Á¡ £È¡ †l¢ „ó¢ Œx£ †¤ Œ¤ ¥ ø«¥ p¤§ ᨠ…÷© {}ª Nùª ÁH« C ¬ ÍN¬ C­ †`­ ®ç­ 9–® ÛЮ H¬² õ² “³ A¤´ @æ´ ¸'µ ൠB~¶ xÁ· ›:¸ ÃÖ¸ ›š¹ [6º 4’º ¨Çº ¦p» U¼ [m¼ xɼ [B½ Už½ ¸ô½ ­¾ è/¿ ³Á RÌÁ R Cr ¶Â ITÄ ÄžÄ ~cÅ WâÅ [:Æ ]–Æ žôÇ 7“É ¤ËÊ ZpË ìËË |¸Ì K5Í ÙÎ Y[Ï aµÏ ËÐ @ãÐ ¬$Ñ ¾ÑÑ ãÓ <tÔ ¼±Ô ?nÕ F®Õ …õÕ R{Ö ZÎÖ ])× “‡× KØ ´gÙ  Ú ¸½Ú ¤vÛ rÜ ÊŽÜ YÝ ?ÙÝ Þ ‰›ß a%á ‡á Qšã Cìã 0ä iMå „·æ €<ç L½ç W è bè Ué Õé Göê ‚>ë [Áë Jì •hì wþì Ivî ¤Àî ½eï [#ð ]ð PÝð F.ñ Suñ ^Éñ S(ò 4|ò U±ò ²ó ?ºõ „úõ …ö P÷ VV÷ ­÷ »÷ Ï÷ é÷ $ ø .ù c2ù –ú ±®û F`ü §ý †®þ 5ÿ °M ºþ ¹ ÎÙ @¨ Hé `2 “   ˹ &… q¬ E ?d \¤ h j º€ ç; g# ^‹ dê äO ‘4 Æ öÍ Ä ŒÆ dS ¸ ÿV! V" ^e# `Ä# %% I-% /w& c§& c ' `o' 8Ð'  ( ( .)( ÈX( „!) £¦* =J- 8ˆ- ‘Á- vS0 ~Ê0 àI2 N*4 oy6 Gé8 Þ19 ; @'; Uh; *¾; é; [< à_= œ@> ŠÝ> Kh@ 6´@ ñëA ÝB êB ñB C C ËC ëD  E Á&F èG ùI µûI N±J þL EÿL .EM 3tM ¨M HµN AþN K@O !ŒO 8®O .çO NP eP "rP K•P ûáQ ÝT >øT [7U N“U âU îU EV yGV UÁV @W “XW ˜ìW …X ΞX .mY 'œY ÑÄY –Z 0«[ 3Ü[ ¶\ ÎÇ\ –_ _ °_ C½_ 1` 33` »g` b#a ˆ†b fc vc ¨‚c +e H8e ðg \rh ]Ïh ð-i ªk Ék bÙk {~ ãÓ~ ·  Í Ïn„ ·>… Xö† "O‡ )rˆ 䜈 ͉ jOŠ ºŠ 'ÄŠ Xì‹ ›E já $LŽ #qŽ [•Ž ßñŽ Ñ KÔ ‘ ,‘ ]M‘ «‘ dµ‘ Å’ à’ Ìö’ £Ã” #g• b‹— ßî˜ «Κ 2z ï­ž ÓŸ Êq¡ Æ<¢ û¤ ¬ÿ¤ 8¬¥ å¥ )ÿ¥ W)¦ ¦ zާ 1 ¨ i;ª m¥ª B« V« °a« ¬ '® L>¯ %‹¯ ;±¯ Kí¯ 9° )<° 6f° ³° Q± _Ó´ Ê3· 'þ· î&¹ žº f´º °» J̼ ƒ½ n›½ Ç ¿ Ò¿ ØÀ žøÁ — ç°Ã ­˜Ä žFÅ oåÅ ¿UÇ ŠÈ Ð È IqÉ »É VÃÉ «Ê KÆÊ îÌ èÍ ÓêÍ '¾Ï æÐ “Ñ ˜Ò œÓ =ºÓ ©øÓ ‡¢Ô Æ*Õ ÈñÕ ÌºÖ b‡× ¥ê× ¼Ø MÙ ~aÙ àÚ °ûÚ |¬Û :)Ü dÝ ¬mÝ Þ Ï+Þ üûÞ <øã *5ä E`å E¦å `ìå Mç =Þç œè _¹è ]é wê jê Sìê u@ë ½¶ë btì _×í û7î (3ï <\ï _™ï &ùï } ñ »žò !Zõ v|ö _óö S÷ \\ø ù¹ù [³ú û ©ü QÈü Vý Dqý "¶ý ôÙÿ nÎ=TEg®­\@mý®¬³»?Â%( ó¶ 'ª 3Ò € ȇ °P U{WmÓRA–”+>3•r$-w=µÆ”Ö›k•)®xØpQÖ™´ »È ØæâÉØÜ=µGó¿;8ûI4=~¼ 9Ø Ü#ï#%!&”8')Í'ï÷'.ç( )o7) §+æ³+^š,ù->{/º/U×1 -2F:33‘3 ©3´3Ñ3Aï314A4 I4U4Åm4L36Æ€6"G8Ej8C°8ô8 :Á&:Îè;·<IÐ=±> Ì>Ö>(ð>? /?‘ߟz 3™ Í øÜ¡MÕ¢þ#£t"¥`—¥$ø¥Ä¨?â¨p"©6“ªaÊ«,­ÈF®¼±@̱S ²@a²@¢²~ã²:b³(³LÆ´é¶ký¶5i·⟸¨‚¹e+»»‘¼¦M½ô½§¿½¸¿òvÀ]iÁCÇÁ@ ÂLÂY̶&ĘÝÄvÅ1†Æø¸Ç±ÈHÎÉcÌT{ÍåÐΦ¶Ïe]Ð’ÃÐ VÒ±cÕÖg1×I™×~ã×›bÙÊþÙÉÛcÑÛy5ÜÀ¯ÝQpÞrÂÞI5ßJßiÊàë4á– â ·âØã]ZäŸäQ~åGÐæ®ç_ÇçQ'èØyèZRê¿­ëBmì°ìAí)Bîwlð`äñ EòèRò;ó‡QóÏÙó©ô"¼ô»ßô ›õ'¥õCÍõDöÌVö•#÷¹÷ÿWøxWùhÐúX9û3’û/Æû2öûB)ü¢lüÿ˜ÿ.¬ÿöÛÿÒDÚ¼'ÜÏ$Ô÷ù[ñ·M— þ hœ ­IÉXlx‚NûsJ}¾ï<‹,‰¸(Bk‰o`ùZ]êÉH]Tp ÅÞf §E!Êí!¾¸#¦w$P%¼o%ù,&&'&F'm'}'•'š'!·'Ù'ë'û' (8(2X(A‹(Í(é(ÿ() #)<-)j)ˆ) ‘)Ÿ)3±)å)õ)&*#+* O*9\*–* ¥*¯*Á*È*)æ*+ !+6-+d+u+‰+ž+¼+Ö+ñ+*,2,Q,p,…,¡,´,Ê,ã,---#-™)-ÍÃ.I‘/9Û/+0^A0I 07ê0»"1"Þ1Õ3±×3³‰4=5“\6ð7ü:hÿ:bh;´Ë;Æ€<{G=IÃ>t @‚@]AËpA\d‘d¥d#¿d%ãeÜ f¾æfÓ¥gËyhœEi>âiU!juwjWíj#EkÈikE2lZxl,Ól m}qÉŒqsVtëÊtQ¶u=vbFv>©wlèwUxQixÍ»x£‰yä-z{a0~B’~AÕ~Wµo:%€œ`žýƒgœ„v…2{…u®…¼$†-á†|‡Œ‡’ˆÀ­ˆ4n‰£‰¡·‰RYв¬ŠF_Œ¿¦Œ`fŽHÇŽhÏyNIµ˜»N‘ˆ ’““w§“O”!o”‘”l¯”#•O@—Ò—Gc˜V«˜b™e™±zš@,›°m›ÌœZëœVFožýžk‹ŸJ÷ŸiB¡e¬¡¢]"£i€£i꣮T¤¥4…¥%º¥à¥¦§Ë.§ú¨}ª]—¬Lõ¬žB­má­fO®e¶®4¯”Q¯Læ¯i3°f°i±Ln±b»±S²]r²Òв¡£³“E´öÙµqзõB¸a8¹aš¹fü¹RcºG¶ºãþ»â¼ë¾ÿ¾¿F³¿ºú¿§µÀÇ]Áè%Ä™ÇѨÇfzÉSáÉ­5ÌZãÌ>Í@XÍǙ̈́aÏæÏuýгsÑv'ÒžÒK´Ò¨Ó}©ÔÍ'ÕpõÕkfÖsÒÖ±F×Hø×;AØ9}ØT·Ø Ú”,ÚZÁÚ@Ü]ÜösÜXjÞDÃÞYßbß¼tßì1àRáoqáSáá~5ãV´ã‚ äŽäGåÜdåAæcUç¹çQºèv éoƒé#óé‘ê©êQÅêµì¬ÍìTzíÏíiíîWïSoïÃïIÚòÌ$óMñóX?ô_˜õsøöMl÷|º÷ï7ø'úBEûîˆûwýVzþÔÑþ¦ÿf¼ÿT#xSŽùâHÜE%[kXÇe b†0éækämKRQžHð69*p$›!Àâ>þ'= -e -“ *Á ì 3ó S' !{ ! >¿ Kþ 'J <r 1¯  á  ì  ø   %' M +d  ©  5Ü = ?P W Wè ]@]žü&,8)e/*¿uêO`$°!Õ÷3EJJYÛ'53]3‘0Å3ö*N1 €*¸4Ï9"Vy8™"ÒLõ2BuD|DÁf#4Š%¿%å( $4EY0Ÿ5Ð7F>"…&¨Ï9ë%*9{d à ,*=W6•!Ì-î-JcU›ñ69H!‚3¤9Ø09C?}½2Î+<-j}5•0Ë!üI 6h !Ÿ Á  Ý þ I!V]![´!H"1Y"‹"o›"˜ #?¤#Cä#($C$a$ $¢$d©$% %%%"E%2h%2›%Î%%ã%. &/8&/h&3˜&1Ì&2þ&E1'w'M–'7ä'T(q(Š(+ž(1Ê(ü(N)ªd)*T'*1|*-®**Ü**+H2+'{+$£+È+cç+;K-‡-›-'­-dÕ-e:.T .Uõ.K//d/”/0ª/Û/Eò/780Bp0 ³0.Ô071¼;1Æø1O¿2w3­‡3k54f¡4‰8ƒ’8€9Ò—9Vj;WÁ;c<¦}?P$AçuAq]BƒÏBrSC!ÆCQèD :EBDE.‡E'¶EÞE#`F$„F8©F.âFG 'G<1GAnG°G ÐGBñG64HOkH>»HfúH<aI<žI9ÛIJJ"`J9ƒJD½JXKC[K'ŸKÇKPàK41LAfLF¨LZïL;JM6†M>½M7üM-4N?bN_¢N5O-8O0fOF—O<ÞOMP1iPb›PGþP/FQWvQVÎQV%R]|RiÚRBDSE‡S`ÍSB.TCqT$µT?ÚT3UBNUE‘UH×UK V?lV;¬V?èV0(WMYW`§WQX<ZX3—X9ËXGYHMY<–Y5ÓY< Z<FZ-ƒZ1±Z9ãZN[0l[d[F\?I\?‰\AÉ\Z ]*f]4‘];Æ]6^(9^5b^G˜^Nà^9/_Bi_6¬_:ã_D`c`_ƒ`6ã`-a@HaP‰aŠÚaAebh§bZcMkc_¹c'dNAd7d=ÈdAe7HeN€e-Ïe'ýe-%f+Sf(f5¨f3Þf7g3Jg:~g?¹gMùg.Gh7vh9®h4èh3i*Qi)|i+¦i,ÒiTÿiCTj9˜j5Òj1k3:k+nk+šk-Æk0ôk1%l4WlCŒl2Ðl0m*4m>_m-žm3Ìm/nA0nXrn9Ën+o'1oYoGyoYÁo*pAFpDˆp3Íp]q_q-xqQ¦q;øq4r0Sr?„rKÄr6sGs]s ds4qsI¦sTðsEt\`t?½tIýt4GuI|u@Æu1v=9vmwvåvBõv8w$TwywB™w[ÜwQ8x<Šx6Çx þx+y+4y(`y+‰y:µy(ðy0z?JzŠz9§z,áz1{$@{e{<{%¼{-â{|3&|Z|"s|–|`µ|!} 8}*E}`p}eÑ}%7~]~/z~ª~B±~6ô~-+Y+y0¥+Ö-€.0€ _€i€%}€£€?ÀH3L0€B±Bô07‚<h‚S¥‚6ù‚80ƒ0iƒšƒB°ƒ0óƒT$„Ny„RÈ„…(3…\… v…%—…/½…í…4 †>†O†k†+†.­†`܆Y=‡W—‡/ï‡(ˆ'Hˆ9pˆªˆ5»ˆ6ñˆ#(‰6L‰#ƒ‰0§‰!؉*ú‰*%Š;PŠ"ŒŠF¯ŠQöŠEH‹QŽ‹:à‹9Œ;UŒ9‘Œ>ËŒ8  CCO(“ ¼Æ â+ð ŽN=ŽŒŽZ«Ž% =J*eK:Ü7BO'’=º3ø(,‘?U‘?•‘,Õ‘1’·4’"ì’=“WM“C¥“/é“”%3”DY”ž”Bº”2ý”!0•BR•••E®•$ô•N–+h–(”–½–2Ö– —"—¸9—ò—# ˜<0˜&m˜”˜U­˜N™KR™`ž™nÿ™KnšºšUÍš.#›MR› ›-»›8é›#"œ/Fœ?vœ=¶œOôœYD9ž6Ø9žçIžL1Ÿ*~ © _» ¨¡zÄ¡!?¢a¢3}¢3±¢å¢£$ £E£"L£,o£ œ£/¦£6Ö£3 ¤AA¤ƒ¤/ ¤Ф+Ù¤W¥7]¥'•¥*½¥!è¥ ¦6+¦9b¦Tœ¦!ñ¦§"&§4I§'~§0¦§×§=ô§#2¨<V¨>“¨+Ò¨þ¨C©MU©9£©MÝ©<+ª!hªŠª1©ªIÛª0%«2V«H‰«!Ò«$ô«0¬3J¬6~¬*µ¬<à¬6­HT­ ­¨­9¯­&é­A®ER®3˜®Ì®6è®?¯6_¯+–¯'¯ê¯B°CI°9°-ǰ$õ°B±>]±=œ±6Ú±-²?²ZG²?¢²Bâ²*%³!P³'r³Oš³4ê³:´-Z´'ˆ´V°´µ0µ$Hµ-mµ'›µ8õ#üµ ¶"?¶!b¶!„¶'¦¶ŸÎ¶n·M~·FÌ·I¸$]¸6‚¸%¹¸9߸C¹]¹0y¹-ª¹6ع'º7ºPºoº1Žº9Àº9úºD4»Oy» ɻֻ:ô»\/¼BŒ¼+ϼ<û¼,8½6e½?œ½Qܽ,.¾[¾1{¾I­¾4÷¾S,¿,€¿­¿)Ê¿)ô¿'À)FÀpÀ‰À&ŸÀ2ÆÀ]ùÀ*WÁ*‚Á$­Á8ÒÁ9 ÂBEÂ)ˆÂ(²Â0ÛÂ9 ÃFÃEcÃ&©ÃÐÃ'ãÃ' Ä13Ä#eÄ*‰Ä´ÄÌÄ.äÄ<ÅPÅGfÅ ®Å,¸ÅåÅ.Æ30ÆdÆ ƒÆ1¤Æ(ÖÆÿÆNÇ@dÇI¥ÇïÇ1È58ÈnÈ$‹È2°ÈãÈ8óÈG,É)tÉ=žÉBÜÉ%Ê5EÊ%{Ê2¡Ê*ÔÊ!ÿÊE!Ë5gËMËBëËG.Ì ṽ̲ Ì,SÍ#€Í&¤Í<ËÍ]ÎfÎ0…Î&¶ÎUÝÎ3ÏSÏ-sÏ6¡Ï1ØÏ= ÐBHÐD‹Ð'ÐÐSøÐ#LÑ€pÑ!ñÑ-Ò'AÒXiÒHÂÒ6 Ó=BÓ@€Ó6ÁÓ9øÓ2Ô<MÔ ŠÔK—ÔãÔóÔ< Õ3FÕ]zÕØÕBôÕ7ÖLMÖIšÖHäÖ?-×%m×!“×µ×%Ó×1ù×-+Ø*YØ:„Ø'¿Ø'çØ6Ù/FÙFvÙ½Ù:ÐÙ Ú(Ú9Ú TÚ1uÚ§Ú!ÀÚBâÚE%ÛFkÛN²ÛÜ Ü %Ü"3Ü"VÜyÜ'ܧÜ,¸Ü/åÜ*Ý$@Ý7eÝ;Ý"ÙÝ?üÝ%<Þ%bÞ5ˆÞ?¾ÞEþÞ)Dß nßZxß[Óß=/àmà ‰à”à#¬àÐà3ìà á-*á#Xá|á›á¹áËáßá;öá82â+kâ!—â ¹â!Úâ#üâ' ãHãfã#„ã ¨ãÉãäãä/äLä8gä ä>³ä òä0å 1å!?å aå0oå& å=Çåæ æ5:æ!pæ’æ £æ°æÐæåæç%ç5çRç,ZçC‡çËçâç:ýç8è4@è!uè—è°è-ÐèÇþèÆé&Úë+ì-ìXLì'¥ìÍì0ÖìQíKYí6¥íYÜíJ6î?î<Áî9þî18ïjï!†ï"¨ï)Ëïõï ð-$ðRð-lð?šð!ÚðÁüð)¾ñ#èñ' ò04ò-eò'“ò»ò*Ñòüò:ó.>ó,móšó<²ó?ïó/ôIMôA—ô/Ùô% õG/õ1wõA©õëõYöSZö6®öåö9÷D>÷Eƒ÷6É÷)ø%*øPø<hø9¥øßø4}ù?²ù?òùX2ú'‹ú6³ú9êú%$û'Jû.rû2¡ûQÔûG&ü-nü,œü,Éü'öü0ý'Oýwý`ýEñý7þ9Sþ'þ*µþ'àþÿÿ!ÿ9ÿXÿnÿIŠÿQÔÿ;&8b›/µåNùNH"—"ºAÝ>^At¶"Ë:î)%E(k”´Ç.ã.A[(k@”ÕZòM1hš<ª4ç7+TF€*ÇCò06#gW‹ã<ó0L'h!2².å 2 LO Èœ de LÊ a Ky 2Å Àø M¹/G737³Oë,;#h3Œ(À:é[$-€-®-Ü $)9N6ˆ-¿TíB?X!˜3º3î"$>c0w6¨*ß* 652lBŸâ,û(,A'n–?­'í-aC$¥XÊÃ#ïç=×C(YZ‚$Ý-7ueAÛ#A'`ˆ£%'D!lŽV¥OüL h N„ "Ó ö &!!/!Q!Nq!À!$Ù!Iþ!H"["*z"'¥"/Í"0ý"$.#6S#3Š#K¾#E $)P$z$(–$'¿$ ç$-ñ$3%HS%6œ%RÓ%6&&*]&0ˆ&?¹&ù&! '/'&J'?q'#±')Õ'Jÿ' J(Ak(<­(;ê(&)U?)I•)_ß)7?*!w*:™*,Ô*++-8+6f+Z+-ø+-&,GT,œ,8´,Ví,'D-Al-®-&À--ç-).b?.`¢.b/@f/'§/3Ï/600:0-k0,™0Æ06ß0*17A14y1U®192'>2Mf2@´2>õ26430k3œ3-¼3_ê3J4bj4SÍ4>!50`5(‘5@º54û56067g6%Ÿ62Å65ø6!.7-P78~7(·7Hà7c)8'84µ8ê8T9ZY9+´9(à9 :_(:+ˆ:!´:0Ö:K;*S;F~;eÅ;E+<!q<“<?¬<9ì<9&='`=*ˆ=7³=ë=:>B>+_>=‹>3É>]ý>_[?'»?-ã?2@D@@`@g¡@- A(7A-`A'ŽA(¶A%ßAB0"B(SB-|B0ªBQÛB-C:LC;‡C'ÃC:ëC&D@EDY†D"àDE="E]`E0¾E=ïE7-F(eF3ŽF]ÂFZ GG{G-ÃG1ñG#H1BHctH1ØHT I._I4ŽI1ÃI2õI(J*?J6jJ¡J¸J9ËJ$K"*KVMK^¤K`L[dL?ÀLfM?gM?§MHçMQ0NB‚NSÅNO73ORkON¾OI PUWPS­PRQRTQ7§Q ßQVíQ-DR!rR"”R"·RUÚRQ0SL‚S[ÏSO+T){Tœ¥TZBUtU8V–KWÍâW_°XÐYmáY–OZ¿æZŒ¦[U3]U‰]Ÿß].^.®^Ý^,á^_._ZD_!Ÿ_`Á_W"`-z`"¨`PË`/a3La.€aY¯aB b7Lb7„b+¼b%èbEceTc$ºc!ßc*d-,d#ZdP~dQÏd!e3=e!qe*“e3¾eBòe?5fFufC¼fSgTg:dg9ŸgÙga÷gÄYhïi?j'Nj-vj'¤jBÌjNk0^k*kºk-Ùkl!&l!HlFjl$±lÖl)õl)mTIm;žm9ÚmQn=fn$¤n/Én<ùn66o^moÌoço^ëo/Jp_zp6Úpq2,q_q'qq"™q#¼qMàq..r]rxr ˜r(¹r(âr( s14sfs;†sÂsSÞs`2t<“t#ÐtEôt?:u-zu4¨u%Ýuv&"v3IvF}v=Äv4w+7w:cwžw'¥wÍw1ìw)x8Hxx.—x2Æx2ùxP,y<}y(ºy0ãy9z$Nzsz6’z)Ézóz+{A3{Hu{;¾{-ú{@(|Oi|4¹|*î|3}M};f}*¢}0Í}Bþ}?A~*~¬~*Ë~!ö~?X3w6«Bâ%€'>€!f€ˆ€9¤€Þ€Eý€-C$q$–D»-‚-.‚D\‚¡‚\±‚+ƒ7:ƒ9rƒ^¬ƒU „9a„3›„HÏ„B…/[…6‹…Â… Ü…6ý…4†S†!i†0‹†I¼†;‡MB‡Y‡8ê‡+#ˆ0Oˆ€ˆ—ˆj±ˆO‰Ml‰nº‰K)ŠuŠ0ŽŠ¿ŠÓŠ=ðŠ(.‹8W‹S‹7ä‹@ŒA]Œ4ŸŒ:ÔŒEBUT˜íý'Ž9=Ž9wŽ3±Ž9åŽ9,Y-†"´×÷ .#RYdy ÞKìH8‘(‘"ª‘Í‘-æ‘!’-6’)d’GŽ’=Ö’ “"“)A“ k“Ox“6È“0ÿ“K0”I|”IÆ”F•OW•$§•-Ì•3ú•0.–6_–-––RÄ–=—<U—*’—½—6Ä—Iû—?E˜X…˜0Þ˜7™G™&W™~™0™-Ι8ü™T5šKŠšFÖšJ›1h›5š›=Л5œ%DœæjœæQ?8ž>xžA·ž ùžŸ"Ÿ?Ÿ3VŸ8ŠŸ*ßîŸLþŸK $d O‰ ?Ù  ¡,&¡1S¡5…¡»¡)Ò¡#ü¡# ¢D¢5b¢/˜¢!È¢ê¢ý¢.£dK£°£AË£A ¤0O¤.€¤-¯¤.ݤ ¥1!¥(S¥-|¥Hª¥-ó¥a!¦*ƒ¦!®¦zЦXK§N¤§Oó§BC¨E†¨+̨?ø¨@8©y©-™©IÇ©ªO-ª2}ªZ°ªQ «-]«%‹«!±«'Ó«3û«3/¬Zc¬ ¾¬*߬0 ­J;­M†­+Ô­+®,®9G®C®6Å®Wü®-T¯‚¯2“¯DƯ °§°Pð/±8D±5}±+³±Gß±C'²Ak²C­²sñ²Ee³-«³<Ù³6´!M´o´!‹´­´$É´î´* µ8µ!WµJyµĵ0Ôµ¶¶$7¶N\¶P«¶#ü¶ ·<1·n·Š·#ž·'·rê¸6]¹H”¹(ݹJºRQºc¤º@»1I»{»c™»Aý»:?¼8z¼G³¼3û¼3/½Kc½3¯½Fã½-*¾BX¾›¾¬¾0˾ü¾E¿ [¿|¿6–¿9Í¿*ÀU2À:ˆÀ2ÃÀ2öÀ$)Á NÁXÁ(kÁ”ÁB›Á<ÞÁ ÂG%Â.mœ³ÂÏÂ=îÂD,Ã+qÃPÃ'îÃ)Ä&@Ä!gÄV‰Ä5àÄ4Å=KÅA‰ÅBËÅÑÆQàÆ92Ç*lÇH—ÇKàÇ6,È-cÈ<‘ÈKÎÈ É $É/É<GÉ'„É%¬ÉDÒÉ<Ê8TÊNÊDÜÊ+!Ë,MË,zË0§Ë0ØË‡ Ì?‘Ì*ÑÌ@üÌ0=Í'nÍ0–ÍPÇÍ9ÎbRÎ6µÎ!ìÎ$Ð,3Ð8`ÐZ™Ð>ôÐH3ÑF|Ñ)ÃÑBíÑ00Ò*aҌҟһÒÔÒ0óÒ0$ÓBUÓE˜Ó3ÞÓ?Ô$RÔ?wÔ6·Ô3îÔ0"Õ6SÕŠÕF£Õ*êÕ6Ö9LÖ†ÖB¥Ö*èÖ×2×*Q×H|×QÅ×>Ø$VØ?{Ø0»Ø3ìØ$ Ù9EÙ$Ù!¤Ù*ÆÙ*ñÙ-Ú-JÚxÚ!”Ú¶Ú9ÒÚB Û3OÛƒÛ¢Û»Û3ËÛ3ÿÛV3ÜŠÜ.£Ü*ÒÜ(ýÜ9&Ý$`Ý'…Ý-­Ý<ÛÝÞ0/Þ:`Þ?›Þ&ÛÞEß$Hß-mߛߣß5¶ß7ìß)$à5NàZ„àZßà?:á&zá2¡á#Ôá&øá&â>Fâ8…â8¾âJ÷â\BãSŸã óã7ä%8ä#^ä/‚ä²äQÆä3å7Lå$„åH©åòå!æE3æyæ'ˆæ-°æ0Þæç4!çVç'rç*šçGÅç€ è'Žè)¶è?àèR ésé‡é!é-¿éíé9 ê!Dê%fêŒê ªê<·ê6ôêT+ëT€ëÕëIìëO6ì6†ì$½ìQâìK4íZ€í@Ûí*îGî/bî)’î¼îHÛî$ï1=ïVoïGÆï/ðA>ðH€ð&Éððð\ñ!cñ…ñ<•ñÀÒñH“ò6Üò0ó<DóPó7Òó, ô7ô@Gô=ˆô)ÆôBðô63õ?jõZªõ!ö<'ö9dö<žö!Ûö%ýö#÷)9÷c÷%‚÷N¨÷0÷÷H(øTqøYÆø3 ù0Tù.…ùD´ù[ùù!Uúwú9’úÌú<âú<ûF\û.£û-Òû(ü3)üÃ]üZ!ýI|ýEÆý) þ\6þH“þ*ÜþNÿ$VÿC{ÿ-¿ÿNíÿÙ<05Mƒ$¢9Ç/>1%p#–?ºúG*X,ƒ.°6ß-,D0q3¢JÖ)!8KA„`Æ'-C3q-¥@ÓCX.nTBò›5 "Ñ Oô .D Fs (º )ã ( .6 be jÈ -3 Ia y« !% TG Zœ ÷ 5y?¯ï!"8?7x1°0â!3.UL„%Ñ7÷/0CtŽ¥I¬!ö-#Fj#ƒ=§å-43h!›'½å%þ?$6d›-»é-H^ w „ ¥Æ,ä&18j‰¢F¼.)2,\0‰'º6â):I:„¿rÖuI<¿Eü/Br6{%²%Øþ()G(qGš"âF+LxA—$Ù3þ2`;7œ7Ô" K/{—:¶ñV gaDÉ6 TE +š #Æ  ê &ô (!#D!*h!“!%³!"Ù!ü!#"84"8m"%¦"5Ì"# #m:#R¨#!û#+$oI$<¹$5ö$C,%=p%O®%Nþ%+M&Ay&J»&Y'>`'[Ÿ'1û'T-(N‚('Ñ(Mù(TG)Uœ)Aò)34*Uh*a¾*. +_O+C¯+Ró+MF,&”,», Ô,Lõ,B-a-Vz-GÑ-M.:g.8¢.\Û.8/ZX/W³/< 0'H0p0+Œ0?¸06ø0U/1!…1<§16ä1*26F26}2*´2%ß2930?3p3;Œ3*È3 ó3 þ3 4]4&y4" 4MÃ4M53_5<“59Ð5 6<#6!`6N‚62Ñ6>7XC7 œ7\¨7884>8Ds88¸8.ñ8W 9'x9' 97È9N:JO:Dš:ß:Z_;Tº;`<”p<¯=Sµ=‰ >?“>FÓ>U?1p?I¢?Nì?C;@œ@eAY‚AYÜA:6BcqBOÕBG%CLmCTºCZD*jDQ•D@çDD(E7mE6¥E@ÜEBF?`F) F6ÊF‹GŸG.-H.\H>‹H@ÊHO IQ[Ip­IAJ7`J“˜KM,LhzLWãL;;McwMDÛME N-fN3”N3ÈN:üN]7OF•ONÜO1+P:]PA˜PÚPKíP?9Q4yQH®QB÷Q:R2JR9}R8·R0ðR !S<+S3hS)œS·0 ®Ô„]”4¯AA ¯ ž Ü´¹š ­8ªÖ¯üÓ „™Q/¶› O Ò2² HÐÛ K ¼—A* õ#¯Ûh2¬A cä³Ô4à = B Û…Ú  B» flZ RÙŸOŽZ±ÏÈØ }] h¥š = í»  ´€µÿ\m ¼C2$ à $ [Ù ³ v9®ª™ƒ ˆï z f“ vß7ƒ áî•ÖŒ š¾¾ª @KY¾tõ¢89ä Óˆ7ÝB l Ûš‰ ç ¤Í0‚ ˜;Š ·E"s…—Õ Ü¦ïÓ º µ¿ ¿ün û¯ëY TK–=¹QÀ ¬ùâ½ ` Ñ º ®# U %LznW ”xŽ­Å_ ·¥³&>ï° ;=Ð_J]˜ è æI‰õ 3 ,Ÿ-–›Á – Î̶ O ßè Ë+G þ   ¶<D —X? §÷—#E Èž· t – [‡™ËSq Ù m@þ&ÇÓ~YaFÕ·Vùä± S:] ß‘2˜Ù Ãc WkÄF\a*LˆÏê æ" RjÃXÑ¿#ºsÈTL ¦ y5P 3 <é7 `*ø œ h )$ë<Ÿaù} ‡ æi Y¥ äwtdé†{® ÿ ¢Û  a ¯ØLúB¡+ ¨ e‚í*FjbÑ +ÝÒ˜BĶ€³® I™™N«  Oe é ½Y𠯦bÜ  Óª –Nà C î4” ÙSˆ ú ¢ºÔÓ# ë{3 Å Ø Æ¯ à:Ü N9 ¦. el•  È ±EõÿUm¿·m]u ƒ `>†{”b 8 †ç•‰÷÷¿ï?6Pà6Є Ëî̈ ¢ .·âÇš(¿ ¯î cº !¼´¶ ÷fb//û’\%ñ ø>¢ }IœzÆß; ïÒ Ø W5lÌŽ,5& gм‚´fÓXÇ À/ ², ZÓû …cÑë¢Åö (  ú ǹ ª Ž|n ¿› òøø µ¶ b„ü^ Jzœf• >Ì N¦ 5¦ Û á,¨ÞøÙ[îŽ:^—ìZ†# •T¦`„5 P£ W¾ ùF À»È ± Ï s H+ôgµ"Þª ÕÐ+» “Ä (¼§ÉVýoU Î&Îλ ©ôbYP5'ƒÀ Úµ7Š/ç šƒj éå ë_ !æ ’ ž  Ž< ë Å'n q8 ÞO À+wþ {Ó I ðí¤qü —FÆáiêo [H¶) -duàÒTd¤ß ð–%Î’\ ³Kð ˆwRX,›9 d(û ƒQ‚ܲ^`(iã‹5 % j Àõ ðu‘¯ «M< Ž>$ EÂï¹–' ÛÖ +9 Ä –fŒÇ Ð éN ‘¤á¾ Ud'“‹$ ø{³ÌÒÏL ¨ÞúÈ ¾Dl\™F òíá` `3é·k&ê >Æù ƒS,—qµyuñ€ ­^—î8f·«×1Á.Ž­òŒ•¿|ÿ¢â‡e ' “ ä ¯4ê×ÝBÕ Å:îÏD À «Ì…*ëP¨pÚ§ F þ¸Sl¬ , ù­X ¬šgÕÑÀ±Õ¬T½˜H \ ªˆ2«Su­?ïü u?, ÌáḴ ` -„뺛 H ~²Ü l ‰Ç‚w  Ÿ©OÁ¾£~nÿ ¢¯’ /­ Šá+Ü JÙ‹`Ò<t ¡ ¦5û> Õ È > ÂGe . B ~6 gänx_ H å Z »Ÿ|Í÷ ÝF EƒAo6T3ëÍ¢dBÝ}œ ìJ L0þžÉ€ö ×r© % .ò”g Ü3  (M B P•°péØ-ÉÍ ò § ¥q œºj”Î:†§ lØÒ† Ç> ‰kë´ ×µ å ” ¡P 7—êù—b r ð … Uï! Z ÙSMr óäy8 2 3h¨ jíkí ÚPnôfŸn˜g ÿ ¶ÿÒSvûÏ> µáVEŒ2Õ • A ¿Î aI ÙôD FÆØº: ´ô¤ý)ÝØ“ MX y † %Ý 8‹R¾ Á˜Ê»äqy d;Q\Ú¾]o d;0È´@O ^)-»l…q Ó ¢î Ž"`„^ 3r×= o{ VØ­?Éc¹e)óåÿT ™I-(Ûl˜ß ‘ L ‘è™ šï© …ûZ@û $â « Cét x K³ " "Ö= {M¼ 5 wâç‘BçuK‘ ññ 2iµ öæ åi >‘¥ŒK Þ ¦ ã!y‰ØÄ €F sA ° ö åXv ?(Ý J Éûö SßCŒ Íó=;‚([š Ö ó O¥SÑ]5 _ˆÅ×¥g~ ñÂ÷æë ‘oÃùQ!-²g)m‡Ñ~·ºÌñ 9²zË 7L¼“lÍ :Ùkànîž¹ Üx¯/Ò w ¡¤Êǃ* ³ E®ÕØ ýä , ñÓÓ½ ÏrXj åÏK¹5 )¹ÿa>1® ø#{Ë‹m#–Àûs*GHi u¡”w( )O ߒɶ2 o Ò  »;­Ó¬ Á‘N ý ¾ { œÂeø$T œês Ð ¼`rÍõâ<{ЬÔq¨s‡: ÒÞäÔUô<ÆM'-ìº,.ËÉ N® ~`'–6 -7 ¨ Ð 5 : Ú|Øgæ‘c®3à 3'oa Ù  "ûí î ¥ õ ÉgFÆÜ ( ò *÷ Æ,T éÊ:u§ëß|úN¦ Y Ê6JXMv8 C ùÔE ƒô rë:. W ê: é ç"¢>ö {»½©¡ÚÍx  ¦QDPç"’ æ4p Â]\øj !à}£¼ ^›YRÙ ‘ ” ' æúõ%´Œí·«oQiÚ Š% NÜØiÈ)< > &/:/ÔoÅ4 ²@ î ˜ &,½þC`½ =ß ý Aë' l³<_PjFž ›&› Mý±ËWqv#H o‡ | mV&tœ?âz^‘ãôTw Ñ ÷Kæ ‰˜èã¥ Ï ðw àèl• A Ö sÈz)L ½•ó %u^ à 9’ÜÊ ]iW¸ k Œ‰ ÁõƒåËm1º  éërõhW Ö9÷ j ã 9œ: hÑHQ Æû·‡K‡ Mãå à ¶BÌ@z£ 1 €‚l±pe I ãÛ&^Ï€êY Þ Šç© ñ‡äÌÒ ÂýŠèy qY “ âJ[wø}¾¦‹ À?Cu > á x°1©óþ Õ^Áè9 ý û‡ ˼ÿäÓ Ã A|£Ì ¦=ü¬ õAÎ ª¸e Ä| ‘ú ”°r æ x ”eyÓ³ yâ$ ⸠„ ª%ðå úÆî¾@Õ) ãÕÓ†V 7ß_X/µJ› bÂÆ [ç ]~-¤ ÂE á _Y¬¾Í; Gë( öÀ ] )¼oˆ}Dõ 8€ ú žJØn ï~I âì â I M^ å.$º0 ý4Ð(D i»’ 3Y$–ï Ñ 6¨® xñ“ ÃBs öŽF<ñŽ‚â hÖðÓŠþ  TülÎ BzZ›Pì » ‘ßm›Ý±Tø ¬²Š˜ý c W¤ ÿO&³ I ï Ä^ ”f…áNñR‚cgå& {˜ VÖ }GîÔÉ ‡ åÐ@Ìù %aÖ² f  ,y ÁQ T NÜ…ÙÜôøIóà ûs(/ ® r© ° ‹'1ö÷Jÿ‘°u{dP  Õ ! ûC(_Ò\ K jq Y BB­ ; í« 6d Û 1rk 'ÄD Ê ° ©³õM)ä G¶î;£ Ÿ /Ñ ÷Ò   ø² ˆ›0 ™ ¡Ö[Ô qZ ]© G} ÷ ÛIÚ ‹Üú Ã" >“17 A!í;sZ*¨‚ B „ ê A© _x? ®#G‰¤>sò· ïâ`u\¶<…Ö¼ d  |Gþ»ô€p  sŠU ˆ ªR h & õ¶×ÇÆC% 0p'2£K ;y¯êî Ëês Cìß A8¿K FÜIZ_rW?§ ðT ‡ Z‚µV ” Î 1 ÖXa•ÇDKà ñøÇ¯ ë ‰ o£ ÓÂ"´Ú¿ hÃv ß €tÁéº&4mË ˜ð dÙ… . aRˆÅOÙbËJ )ÞIIO\è ¶2w TGpI~ N $z ¢à6±i= EtÍþc¡¶õ œ ]<æ ðÒ!ò ÂY¸Ex>Q•wDÀ­›ŒP„à$ŒDò7ã¿“¸M²C x“ÄUXdÓ‘ «v40 k!k1 "ß-á AS P ætó ª¦®3îå ² ãHLný¶ýQg+Œ kÉÚŸ†ê yh Sfã³d• } ¿ ¡šÈô ¥á w §(Ѱg­í}p ¯¬$±Æ ¡´ób L1ô( =•Pt ´¡Ö‘ %pò$díÎk« u#³ŸD$jE –<2_m£¦ P·¿Œ zâÝL¢p½ÂÔž´=î· VNŸ —=;U œ ðO ,Ë¡@Eü Öqœ Q µLŸÆ`è 8{ Ú¥šbc Dÿ(‹ }d  üFT¡ ? s úôù ˜ À+˜lÊÇaàf ja…1,'ÈÀ J0 Ö UˆÚºìô<Ÿµ ÿ ÆZ€Ê )& Náèûiÿ× Ç ™e É #…  •|ÆÈ RÀ&[ Ä ‚ ‰À òÊGrÞ ;‹é ö{A FÉì9p²Õ§  à @ äÊH i ŒÖês 2hù› ùÎH©«%? Úö^ Å™q¨œ‹àÚ pÇ ú“% ¾ Jí‰.$ú ä mÜŒ… n D }tˆ È VZ2Ïéû _ŠRý‰Ø 9’) ˜1 QE íôù<”vv ÍÏ>ÞY"“Áù ©™UU. - yò ‰ ÊÅ— V Ú “˜þ*ZÁ WfŒ ÞF1†ºÕ ’ Ygþi 3öª™ ªœšôeÀ „@4 | Î ‡« ‚¦|f« f @">auD+ bû$ží¬ˆ Š %7Ý*+… mL§{ °ð*ÈßûeµYz  ’6t7 ]V  ŃšÞÅhÕÁ& oh.+› JÂó7 pìM c¸¿× 0¢þΰŠΠ˜ü Äv2ÏÏ øÃײ~ ,ôƒú µbI ^x rnE!Ñaÿø ݆ Èê!®• ¬eD» " ìEZb‹ì§W. -{ FÁ  Z GÔéËnƃ e3¡†Ž ý_h±1Ð :ù‘ œ—™ wMçSòTþ š — ¯¸”æ X Ò¨ ù³¬ ‹ ˆ9 Ì+ú^±Ñ Ë~d?N 8Ûì† 9å*! ŸÕñçpœX /Ž ?¡ ¨ ž É(Kœ 5 lv7€:k Ž %TÀ—U¿ Ì C hEêÉÃ[ PR¥ ‰ kRÿ 6HÍ> ü³< c £Ï©â*ÛÞ ìG è C Œ‹ פohW Ô.ã ŠFS üØ éÑ44î Ò£H ´  } ³…Ú¼¤ ý!Ø ?ŸŠBO0 Á„- ðf‡æ±Ha Z.·çݤ¶C5±¥ Óª ‰ë^æà nÊ"†BǸ ¿Õ{å~ì ²?í|ý † ÷U Wµ _]Ä L ÷*Ê^›®É ºÈ§‡²   D¹Òyp Ï ú )|  `ËÉ©Þ` ×+Iýk Á2 6 Ô ~ !»›ï׃€ ü pÛ@ Ø\¤²‚ Ñ— 8 x«o<,¢ …î Àj y0Þ¢‚e|m § ¾OÁávÙíDu ’.¾êÊ ‚šö* " €N þ3/  þ) 7¼ #n R « |ø’ µq­‡9&Þ|‹zá·#Ô À ÔÍÓ6.k7+ ÝP¸Hà£<l§—ž1¦,¡¥|SP : – "åÔ©ª4 £ ¹êÅ Þ£ z +„¤¾ q›g „ 2ê¹ Ø ~¡˜± vÇ‚Øõ°¦f 0Ç0 æ9HÚ;­ 4- °ö±nAÃãy â6›°VÊÎ ð [Q#}Ë; Þ=Œî6 ¿Õ{Š'Ù­{ýjð •JVæ2ÚñHÑ/òXÂ{~ èŸ X@ —ì ¥ÿ­¹K ΍ Ø6J†ÌŒ xW+ ýU’ í§½µ³ – ï€ ˆ” $‰ãŒo†QÃ]s < zCà84E N ¶· ;¥ñ .çJ e ‘מ ™¹ ,1’iÕš » ¼È:¡ ¬\ CJ¯gЯ _ rH8ÌWF RÙùP Ç0­ Û=[ £ÔÒÖ_MgM ð ` Q ¨ª® ÄB³‹0é G…¸- KîµõTOcÑŸ¥X@ó~µËÅY%ßÐ 7Ö}k jw4 !s çv=ƒ! 0%^q‹ ºI¾çÙ ²YÇ@ùI ¼ß§q‰} k¹äÄ 4 `4q R €Þ½1kÔ¤i í ¢Õ¬ Ìjü Þ Uwt3 É ™ Vm °bQª!R EürU£E öG ¼‚!f&_ð”§T5þp« ÿyp“ÎÄ<Ž4»° ç × /´Mí«qòb ± | $c¢ä$  cIרç. Gä :n åÖ…å2…¦í rÏvø $¤£”ä”.#f5ù®; 8„ {") Àÿ©ËÍ[pô – F p¨  è‚™ÿ„M r_Ü / «? ʸs ÿ × áïe ] ± J2 ²Ù— *Ý † ´ç vðÚûæ¿·Á Nl Ì‹\tU½Í-:¼q|Š š‹wjƒ¾¢ ¸ì6½zA 5/y[½ ¬4à? $Šæm 5™ àgxH P3¶ ç è5aÈ!úÝ"¶ úͶ,¤zŠ È º÷(ë ˆ O \„ â*BwGÄ!;;a Q?~–o U i Ê œÄÖà sÛ= ú¿EU⸠\Å n 5ï 7V "¼ö?²¢•WsYÔ ¸:…âh å„ ªŠ ®™;÷U ] ê b*ÜÛ k ió&ˆ tÆÎ ­ Ì ˆßõaz™½¹€ þ1Ç’* ¸f àjÙ ˜ò Lxã_Ñ'†¬C  ñM+ª  ÙÛ9÷ö>p uû ® #C °9^ú‰æ¾ ¤ öWãé¦Í ç¯ ¹u Rìõü2@ ÔQD NWh ãÒ ó Ž 6w ô ¨ û |Ö Åa \ } ®åNäç'ƒ9.¬Íu }àHóüóX FD »´ ß¾ gé wX“}ï ,®ý¦ G ƒòé‰ü”Ä 0/Å Ï %! Ê ÍX” ¡ MS c¡¥ +ž’Ñ  Ý ä§˜ ãV¤Z × ó1–¶%¼Š ž 7 b Ÿg ì— ;ƒ $t ' ã t> c¯} ` LrÀÄÁ bï £ J L÷l èë“N ·³Tb× á fzš9øc tØv  6ÐGù  ù=Žn_ ©„L Å ¼å3x0R ^ * 4 C«n=\ É[ d 8JO)G 5£_ €‘ó Îü›â × mX‚èX èR7Œ& €-½÷/r S  ¢’ʆ µ d ÑV]z 58Ð8Ü Ž ô < [• áÒ-œád «–§e¹’Ï · ÃÛ i¥]¤ R=h™3ŽaW 0±@¢ a%™ä#  ¡ ˆCc*ãgŸ ¡úÁË â ø x ³@ Æ ¨o/—/B 1má1 [ Ðòž?‰Ï&2 EÄ ½3xÄ“ v'p þº žžr •Y’K ½r ½ »§So+ LÊÌ ƒÞ ½ uë éCöG o ~ø@VÚÛ3­ö <Ò&¤o OQÂÍ É ›c ŸË }t Zjèê- JÍ sçv\¨ÏÔ ¹©ßƒ ihwžb ÷ ÁBó ³\ õÑì?7Ÿ VÝô†ì(Î 4^HñZ » `.K· ê)ó‹ hg # × S ] xö‡"þ  °`3zÊÛ ï²Žã [, jqy ö'¹ M = y¼ :jny# l ¸èÐ ¬ñ Ä´ :ÐŽ×8 ¸ Gð º@" §f 0aéñ §‹ôð¬¹xí Až9R7ñ¬2že»~š* ÿ©#z£# !u[á6 Ý6 c ¨Á £–W 0'Cëò õ¸ Y­B Ål è´4PLW”ó •[/ µ¥tv ¹ž[¸èm+ã•‚iÜÕÝ Ðy¤ A –ŒF9þ€Ÿ5| ¾v ݉K†“)«º 0Kì@Æ Q L»(  GŒ8´’Щbê Ž UQ~ì ÔÃOO Üe ®- õ[ S#“ɇE ðœ°7T˜  ,œm) ; mþ¸ÅM€ý6Îñ Z « °š¯òD’~­½¨Ÿ´ ‡ + cÁã ¨½ª-@ =ïx Þɰ ¿k(‡S÷= ±æý° \ÇÛ± ­ h8u 6´ÏAAÐk¸ „ò  d‹N÷ª–DÓI–  Ì …ˆAÍi —ú8œÃÅ%ÉOüй Ýøt ‡Êtüº].Š9 '² 1 üÇ k“ ó VS3©ed\R ò- Æ VÈ´'Ë w󥄛?m Âè‚ ž¯·“Cñ ¥ Ú Š ÈD ß disabling current template maps extending current template maps overriding default cvs keywordset overriding default svn keywordset configuration using current keyword template maps configuration using custom keyword template maps configuration using default cvs keywordset configuration using default svn keywordset keywords expanded /annotate/{revision}/{path} --------------------------- /archive/{revision}.{format}[/{path}] ------------------------------------- /bookmarks ---------- /branches --------- /changelog[/{revision}] ----------------------- /changeset[/{revision}] ----------------------- /comparison/{revision}/{path} ----------------------------- /diff/{revision}/{path} ----------------------- /file/{revision}[/{path}] ------------------------- /filelog/{revision}/{path} -------------------------- /graph[/{revision}] ------------------- /help[/{topic}] --------------- /log[/{revision}[/{path}]] -------------------------- /manifest[/{revision}[/{path}]] ------------------------------- /shortlog --------- /summary -------- /tags ----- (some details hidden, use --verbose to show complete help) (use 'hg %s -h' to show more help) (use 'hg help %s' to show the full help text) (use 'hg help -v -e %s' to show built-in aliases and global options) (use 'hg help -v%s' to show built-in aliases and global options) (use 'hg help' for the full list of commands or 'hg -v' for details) (use 'hg help' for the full list of commands) Adding a Subrepository ====================== Description =========== Enabled extensions: Examples ======== Final summary: Synopsis """""""" **hg** *command* [*option*]... [*argument*]... To prevent this mistake in your local repository, add to Mercurial.ini or .hg/hgrc: To remove '-' lines, make them ' ' lines (context). To remove '+' lines, delete them. Lines starting with # will be removed from the patch. Write the introductory message for the patch series. [+] marked option can be specified multiple times ``annotate`` ------------ ``auth`` -------- ``defaults`` ------------ ``diff`` -------- ``extensions`` -------------- ``format`` ---------- ``hostfingerprints`` -------------------- ``profiling`` ------------- ``subpaths`` ------------ ``ui`` ------ ``web`` ------- additional help topics: aliases: %s auction for merging merge bids calculating bids for ancestor %s diffs (%d lines): diffs (truncated from %d to %d lines): diffstat: keywords written to %s: use 'hg help -c %s' to see help for the %s command $ ls bar.c foo.c $ hg status ? bar.c ? foo.c $ hg add bar.c $ hg status A bar.c ? foo.c $ ls bar.c foo.c $ hg status ! foobar.c ? bar.c ? foo.c $ hg addremove adding bar.c adding foo.c removing foobar.c $ hg status A bar.c A foo.c R foobar.c $ ls foo.c $ hg status ! foobar.c ? foo.c $ hg addremove --similarity 90 removing foobar.c adding foo.c recording removal of foobar.c as rename to foo.c (94% similar) $ hg status -C A foo.c foobar.c R foobar.c $ ls foo.c $ hg status ? foo.c $ hg add adding foo.c $ hg status A foo.c drop 5339bf82f0ca 3 Zworgle the foobar pick 8ef592ce7cc4 4 Bedazzle the zerlog pick 0a9639fcda9d 5 Morgify the cromulancy hg histedit -r 2 hg histedit -r 3 pick 252a1af424ad 2 Blorb a morgwazzle pick 5339bf82f0ca 3 Zworgle the foobar pick 8ef592ce7cc4 4 Bedazzle the zerlog pick 5339bf82f0ca 3 Zworgle the foobar pick 8ef592ce7cc4 4 Bedazzle the zerlog pick 0a9639fcda9d 5 Morgify the cromulancy pick 8ef592ce7cc4 4 Bedazzle the zerlog pick 5339bf82f0ca 3 Zworgle the foobar pick 252a1af424ad 2 Blorb a morgwazzle Additional information about the possible actions to take appears below the list of revisions. An editor opens, containing the list of revisions, with specific actions specified:: Start history editing from revision 2:: Start history editing from revision 3:: To remove revision 3 from the history, its action (at the beginning of the relevant line) is changed to 'drop':: To swap revision 2 and 4, its lines are swapped in the editor:: The history resulting from -L/--line-range options depends on diff options; for instance if white-spaces are ignored, respective changes with only white-spaces in specified line range will not be listed. hg archive -r 1.0 project-1.0.zip hg archive project.tar.gz -X ".hg*" hg backout -r . hg backout -r 23 hg backout -r 23 --no-commit hg commit -m "Backout revision 23" hg bisect --bad 34 hg bisect --good 12 hg bisect --good hg bisect --bad hg bisect --reset hg bisect --reset hg bisect --bad 34 hg bisect --good 12 hg bisect --command "make && make tests" hg bisect --skip hg bisect --skip 23 hg bisect --skip "!( file('path:foo') & file('path:bar') )" hg book -f @ hg book -i reviewed hg book -m turkey dinner hg book -r .^ tested hg book new-feature hg clone --stream http://server/repo -u 1.5 hg clone -r 04e544 experimental/ good/ hg clone https://www.mercurial-scm.org/repo/hg/ hg clone https://www.mercurial-scm.org/repo/hg/#stable hg clone project/ project-feature/ hg clone ssh://user@server//home/projects/alpha/ hg commit --amend --date now hg commit --exclude "set:binary()" hg commit --include "set:**.py" hg diff "set:added() and grep(GNU)" hg diff --git -r 1.0:1.2 lib/ hg diff --stat -r "date('may 2')" hg diff -c 9353 # compare against first parent hg diff -r 9353^:9353 # same using revset syntax hg diff -r 9353^2:9353 # compare against the second parent hg diff foo.c hg export --git -r 123:150 > changes.txt hg export -r "outgoing()" -o "%n-%m.patch" hg export -r 9353 | hg import - hg files "set:binary()" hg files "set:grep('bob')" hg files -0 | xargs -0 grep foo hg files -I "**/README" hg files -vr . hg files . hg forget "set:added() and binary()" hg forget "set:hgignore()" hg graft -D "2085::2093 and not 2091" hg graft -c hg id --id > build-id.dat hg id -n -r 1.3 hg id -r tip https://www.mercurial-scm.org/repo/hg/ hg import - hg import --config ui.fuzz=7 fuzz.patch hg import --config ui.patch="patch --merge" fuzzy.patch hg import --exact proposed-fix.patch hg import -s 80 http://example.com/bugfix.patch hg import https://www.mercurial-scm.org/repo/hg/rev/5ca8c111e9aa hg import incoming-patches.mbox hg in -vpM --bundle incoming.hg hg pull incoming.hg hg in changes.hg -T "{desc|firstline}\n" hg incoming -vp hg lfpull -r "branch(default)" hg lfpull -r "head() and not closed()" hg log --debug -r . hg log --graph -r "bisect(range)" hg log --removed file.c hg log -L file.c,13:23 hg log -L file.c,13:23 -L main.c,2:6 -p hg log -Mp lib/ hg log -T list hg log -f hg log -k alice -d "may 2008 to jul 2008" hg log -k bug --template "{rev}\n" hg log -l 10 -b . hg log -r "a21ccf and ancestor(1.9)" hg log -r "bisect(current)" hg log -r "bisect(pruned)" hg log -r "bisect(range)" hg log -r "last(tagged())::" --template "{desc|firstline}\n" hg log -r "sort(all(), date)" hg log -r . --template "{node}\n" hg log -v hg rebase hg rebase --base myfeature --dest default hg rebase --collapse -r 1520:1525 -d . hg rebase --source c0c3 --dest 4cf9 hg rebase -r "branch(featureX)" -d 1.3 --keepbranches hg rebase -r 5f493448 -d stable hg status --copies --change 9353 hg status --rev 9353 hg status -an0 hg status -v -t mardu hg status re: hg update stable hg graft --edit 9393 # so convert knows the type when it sees a non empty destination $ hg init converted $ hg convert orig/sub1 converted/sub1 $ hg convert orig/sub2 converted/sub2 $ hg convert orig converted - A file foobar.c was moved to foo.c without using :hg:`rename`. Afterwards, it was edited slightly:: - A number of changes have been made. Revision 2 and 4 need to be swapped. - A number of changes have been made. Revision 3 is no longer needed. - A number of files (bar.c and foo.c) are new, while foobar.c has been removed (without using :hg:`remove`) from the repository:: - New (unknown) files are added automatically by :hg:`add`:: - Specific files to be added can be specified:: :hg:`remove` never deletes files in Added [A] state from the working directory, not even if ``--force`` is specified. %(path)s -----BEGIN CERTIFICATE----- ... (certificate in base64 PEM encoding) ... -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- ... (certificate in base64 PEM encoding) ... -----END CERTIFICATE----- BM1 01234567890a added BM2 deleted BM3 234567890abc advanced BM4 34567890abcd diverged BM5 4567890abcde changed BM1 01234567890a added BM2 1234567890ab advanced BM3 234567890abc diverged BM4 34567890abcd changed hg log -r "p1()+p2()" or hg log -r "p1(REV)+p2(REV)" or hg log -r "max(::p1() and file(FILE))+max(::p2() and file(FILE))" or hg log -r "max(::p1(REV) and file(FILE))+max(::p2(REV) and file(FILE))" hg transplant --branch REV --all public < draft < secret qguard foo.patch -- -stable (negative guard) qguard bar.patch +stable (positive guard) qselect stable :hg:`backout` cannot be used to fix either an unwanted or incorrect merge. :hg:`diff` may generate unexpected results for merges, as it will default to comparing against the working directory's first parent changeset if no revisions are specified. :hg:`export` may generate unexpected diff output for merge changesets, as it will compare the merge changeset against its first parent only. :hg:`log --patch` may generate unexpected diff output for merge changesets, as it will only compare the merge changeset against its first parent. Also, only files different from BOTH parents will appear in files:. :hg:`status` may appear to disagree with diff if permissions have changed or a merge has occurred. The standard diff format does not report permission changes and diff only reports changes relative to one merge parent. An example showing how to convert a repository with subrepositories:: Branch names are permanent and global. Use :hg:`bookmark` to create a light-weight bookmark instead. See :hg:`help glossary` for more information about named branches and bookmarks. Examples: Extra care should be taken with the -f/--force option, which will push all new heads on all branches, an action which will almost always cause confusion for collaborators. For performance reasons, :hg:`log FILE` may omit duplicate changes made on branches and will not show removals or mode changes. To see all such changes, use the --removed switch. If you use --outgoing, this command will abort if there are ambiguous outgoing revisions. For example, if there are multiple branches containing outgoing revisions. Mercurial will not let you commit files with unresolved merge conflicts. You must use :hg:`resolve -m ...` before you can commit after a conflicting merge. Specifying a tag will include the tagged changeset but not the changeset containing the tag. Specifying negative guards now requires '--'. The -c/--continue option does not reapply earlier options, except for --force. Timestamp in seconds is used to decide order of backups. More than ``maxbackups`` backups are kept, if same timestamp prevents from deciding exact order of them, for safety. To check out earlier revisions, you should use :hg:`update REV`. To cancel an uncommitted merge (and lose your changes), use :hg:`merge --abort`. Use "min(outgoing() and ::.)" or similar revset specification instead of --outgoing to specify edit target revision exactly in such ambiguous situation. See :hg:`help revsets` for detail about selecting revisions. Use -L/--line-range FILE,M:N options to follow the history of lines from M to N in FILE. With -p/--patch only diff hunks affecting specified line range will be shown. This option requires --follow; it can be specified multiple times. Currently, this option is not compatible with --graph. This option is experimental. When no hunks apply cleanly, :hg:`import --partial` will create an empty changeset, importing only the patch metadata. ``default`` and ``default-push`` apply to all inbound (e.g. :hg:`incoming`) and outbound (e.g. :hg:`outgoing`, :hg:`email` and :hg:`bundle`) operations. using rollback or extensions that destroy/modify history (mq, rebase, etc.) can cause considerable confusion with shared clones. In particular, if two shared clones are both updated to the same changeset, and one of them destroys that changeset with rollback, the other clone will suddenly stop working: all operations will fail with "abort: working directory has unknown parent". The only known workaround is to use debugsetparents on the broken clone to reset it to a changeset that still exists. # display activity of developers by month hg churn -f "%Y-%m" -s -c # display count of lines changed in every year hg churn -f "%Y" -s # display daily activity graph hg churn -f "%H" -s -c (grafted from CHANGESETHASH) (transplanted from CHANGESETHASH) - Reverse the effect of previous bad revision 23 and leave changes uncommitted:: - Reverse the effect of previous bad revision 23:: - Reverse the effect of the parent of the working directory. This backout will be committed immediately:: - advance the current bisection by marking current revision as good or bad:: - all changesets that touch a directory, with diffs, excluding merges:: - all revision numbers that match a keyword:: - amend the current commit and set the date to now:: - attempt to exactly restore an exported changeset (not always possible):: - briefly list changes inside a bundle:: - change the default fuzzing from 2 to a less strict 7 - changesets ancestral to the working directory:: - changesets showing all modifications of a file, including removals:: - changesets touching lines 13 to 23 for file.c and lines 2 to 6 of main.c with patch:: - changesets touching lines 13 to 23 for file.c:: - changesets with full descriptions and file lists:: - check if a given changeset is included in a tagged release:: - check the most recent revision of a remote repository:: - clone (and track) a particular named branch:: - clone a remote repository to a new directory named hg/:: - clone from an absolute path on an ssh server (note double-slash):: - collapse a sequence of changes into a single commit:: - commit - import - pull - push (with this repository as the destination) - unbundle - commit all files ending in .py:: - commit all non-binary files:: - compare a file in the current working directory to its parent:: - compare a revision and its parents:: - compare two historical versions of a directory, with rename info:: - continue a graft after resolving conflicts:: - copy a single change to the stable branch and edit its description:: - create a lightweight local clone:: - create a repository without changesets after a particular revision:: - create a tarball excluding .hg files:: - create a zip file containing the 1.0 release:: - create an active bookmark for a new line of development:: - create an inactive bookmark as a place marker:: - create an inactive bookmark on another changeset:: - diff all newly-added files that contain a keyword:: - do a streaming clone while checking out a specified version:: - export all the changesets between two revisions to a file with rename information:: - find all changesets by some user in a date range:: - find files containing a regular expression:: - find the revision corresponding to a tag:: - forget files that would be excluded by .hgignore:: - forget newly-added binary files:: - forget the current bisection:: - generate a build identifier for the working directory:: - get a NUL separated list of added files, suitable for xargs:: - get change stats relative to the last change on some date:: - graft a range of changesets with one exception, updating dates:: - import a changeset from an hgweb server:: - import a traditional patch from a website and detect renames:: - import all the patches in an Unix-style mbox:: - import patches from stdin:: - last 10 commits on the current branch:: - list all binary files:: - list all files named README:: - list all files under the current directory:: - list available log templates:: - mark the current revision, or a known revision, to be skipped (e.g. if that revision is not usable because of another issue):: - move "local changes" (current commit back to branching point) to the current branch tip after a pull:: - move a named branch while preserving its name:: - move a single changeset to the stable branch:: - move the '@' bookmark from another branch:: - pull largefiles for all branch heads:: - pull largefiles on the default branch:: - rebase everything on a branch marked by a bookmark onto the default branch:: - rename bookmark turkey to dinner:: - search tracked file contents with xargs and grep:: - see all changesets that took part in the current bisection:: - see all changesets whose states are already known in the current bisection:: - see the changeset currently being bisected (especially useful if running with -U/--noupdate):: - show all changes including copies in an existing changeset:: - show changes in the working directory relative to a changeset:: - show changes in the working directory relative to the current directory (see :hg:`help patterns` for more information):: - show incoming changes excluding merges, store a bundle:: - show incoming changes with patches and full description:: - show revisions sorted by date:: - show the source of a grafted changeset:: - shows sizes and flags for current revision:: - skip all revisions that do not touch directories ``foo`` or ``bar``:: - splice a commit and all its descendants onto another part of history:: - split outgoing changes into a series of patches with descriptive names:: - start a bisection with known bad revision 34, and good revision 12:: - summary of all changesets after the last tag:: - the full hash identifier of the working directory parent:: - use 'make && make tests' to automatically find the first broken revision:: - use an external tool to apply a patch which is too fuzzy for the default internal tool. - use export and import to transplant a bugfix to the current branch:: - you can even get a nice graph:: -A/--after can be used to remove only files that have already been deleted, -f/--force can be used to force deletion, and -Af can be used to remove files from the next revision without deleting them from the working directory. 1. Explicitly select them using ``--rev``. 1. If no option is specified, and if the requested changeset is an ancestor or descendant of the working directory's parent, the uncommitted changes are merged into the requested changeset and the merged result is left uncommitted. If the requested changeset is not an ancestor or descendant (that is, it is on another branch), the update is aborted and the uncommitted changes are preserved. 2. Use ``--source`` to select a root changeset and include all of its descendants. 2. With the -m/--merge option, the update is allowed even if the requested changeset is not an ancestor or descendant of the working directory's parent. 3. Use ``--base`` to select a changeset; rebase will find ancestors and their descendants which are not also ancestors of the destination. 3. With the -c/--check option, the update is aborted and the uncommitted changes are preserved. 4. If you do not specify any of ``--rev``, ``source``, or ``--base``, rebase will use ``--base .`` as above. 4. With the -C/--clean option, uncommitted changes are discarded and the working directory is updated to the requested changeset. :``added``: pull will create it :``advanced``: pull will update it :``diverged``: pull will create a divergent bookmark :``changed``: result depends on remote changesets :``added``: push with ``-B`` will create it :``deleted``: push with ``-B`` will delete it :``advanced``: push will update it :``diverged``: push with ``-B`` will update it :``changed``: push with ``-B`` will update it = ========= == == == == opt/state A C M ! ========= == == == == none W RD W R -f R RD RD R -A W W W R -Af R R R R ========= == == == == ? - display help Before version 1.7, the behavior without --merge was equivalent to specifying --merge followed by :hg:`update --clean .` to cancel the merge and leave the child of REV as a head to be merged separately. By default, the pending changeset will have one parent, maintaining a linear history. With --merge, the pending changeset will instead have two parents: the old parent of the working directory and a new child of REV that simply undoes REV. Examples: For efficiency, hardlinks are used for cloning whenever the source and destination are on the same filesystem (note this applies only to the repository data, not to the working directory). Some filesystems, such as AFS, implement hardlinking incorrectly, but do not report errors. In these cases, use the --pull option to avoid hardlinking. For example, the following commands are transactional, and their effects can be rolled back: For remote repository, using --bundle avoids downloading the changesets twice if the incoming is followed by a pull. From the point of view of pulling behavior, bookmark existing only in the remote repository are treated as ``added``, even if it is in fact locally deleted. From the point of view of pushing behavior, bookmarks existing only in the remote repository are treated as ``deleted``, even if it is in fact added remotely. K = keyword expansion candidate k = keyword expansion candidate (not tracked) I = ignored i = ignored (not tracked) M = modified A = added R = removed C = clean ! = missing (deleted by non-hg command, but still tracked) ? = not tracked I = ignored = origin of the previous file (with --copies) Mercurial will update the working directory to the first applicable revision from this list: On Windows, this configuration option is ignored and the command aborted. See :hg:`help revisions.bisect` for more about the `bisect()` predicate. Some examples: The -C/--clean, -c/--check, and -m/--merge options control what happens if the working directory contains uncommitted changes. At most of one of them can be specified. The ``.hgsubstate`` file should not be edited manually. The action taken locally when pulling depends on the status of each bookmark: The action taken when pushing depends on the status of each bookmark: The following table details the behavior of remove for different file states (columns) and option combinations (rows). The file states are Added [A], Clean [C], Modified [M] and Missing [!] (as reported by :hg:`status`). The actions are Warn, Remove (from branch) and Delete (from disk): The rollback command can be entirely disabled by setting the ``ui.rollback`` configuration setting to false. If you're here because you want to use rollback and it's disabled, you can re-enable the command by setting ``ui.rollback`` to true. To avoid permanent data loss, rollback will refuse to rollback a commit transaction if it isn't checked out. Use --force to override this protection. When cloning from servers that support it, Mercurial may fetch pre-generated data from a server-advertised URL or inline from the same stream. When this is done, hooks operating on incoming changesets and changegroups may fire more than once, once for each pre-generated bundle and as well as for any additional remaining data. In addition, if an error occurs, the repository may be rolled back to a partial clone. This behavior may change in future releases. See :hg:`help -e clonebundles` for more. With -B/--bookmarks, the result of bookmark comparison between local and remote repositories is displayed. With -v/--verbose, status is also displayed for each bookmark like below:: a) null if -U or the source repository has no changesets b) if -u . and the source repository is local, the first parent of the source repository's working directory c) the changeset specified with -u (if a branch name, this means the latest head of that branch) d) the changeset specified with -r e) the tipmost head specified with -b f) the tipmost head specified with the url#branch source syntax g) the revision marked with the '@' bookmark, if present h) the tipmost head of the default branch i) tip alternatively, use --config merge.preferancestor=%s d - done, skip remaining changes and files a - record all changes to all remaining files q - quit, recording no changes exclude path/to/file-or-dir 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 # 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 -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 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 qguard other.patch -- +2.6.17 -stable hg qimport -e existing-patch -n new-name include path/to/file-or-dir key parent1, parent2 original_branch_name new_branch_name rename path/to/source path/to/destination s - skip remaining changes to this file f - record remaining changes to this file source author = destination author y - record this change n - skip this change e - edit this change manually HG: ------------------------ >8 ------------------------ The tempfile mechanism is recommended for Windows systems, where the standard shell I/O redirection operators often have strange effects and may corrupt the contents of your files. hg log --template "{rev} {phase}\n" hg log -r "not public()" hg phase --draft "secret()" hg phase --force --draft . hg phase -fd "outgoing(URL)" path/to/nested = [git]git://example.com/nested/repo/path path/to/nested = [svn]https://example.com/nested/trunk/path path/to/nested = https://example.com/nested/repo/path "identity" means the name is derived from the first changeset in the repository. In this mode, different remotes share storage if their root/initial changeset is identical. In this mode, the local shared repository is an aggregate of all encountered remote repositories. "remote" means the name is derived from the source repository's path or URL. In this mode, storage is only shared if the path or URL requested in the :hg:`clone` command matches exactly to a repository that was cloned before. $ hg log -r1 --template "{node}\n" b56ce7b07c52de7d5fd79fb89701ea538af65746 $ hg log -r1.0::1.1 --template changelog (Alternatively, you can use ``--abort`` to abandon an unshelve that causes a conflict. This reverts the unshelved changes, and leaves the bundle in place.) (For more information about the phases concept, see :hg:`help phases`.) (Verb) Diffing two changesets is the action of creating a diff or patch. (Verb) The act of recording changes to a repository. When files are committed in a working directory, Mercurial finds the differences between the committed files and their parent changeset, creating a new changeset in the repository. (Verb) The action of creating a child changeset which results in its parent having more than one child. (Verb) The process of creating a clone, using :hg:`clone`. (Verb) The process of using a patch file to transform one changeset into another. (Verb) This term is usually used to describe updating the state of the working directory to that of a specific changeset. See :hg:`help update`. (Verb) Updating the working directory to a specific changeset. See :hg:`help update`. (default: False) (default: True) (default: ``$EMAIL`` or ``username@hostname``. If the username in hgrc is empty, e.g. if the system admin set ``username =`` in the system hgrc, it has to be specified manually or in a different hgrc file) (default: topic bar number estimate) - :hg:`resolve -l`: list files which had or still have conflicts. In the printed list, ``U`` = unresolved and ``R`` = resolved. You can use ``set:unresolved()`` or ``set:resolved()`` to filter the list. See :hg:`help filesets` for details. - :hg:`resolve -m [FILE]`: mark a file as having been resolved (e.g. after having manually fixed-up the files). The default is to mark all unresolved files. - :hg:`resolve -u [FILE]...`: mark a file as unresolved. The default is to mark all resolved files. - :hg:`resolve [--tool TOOL] FILE...`: attempt to re-merge the specified files, discarding any previous merge attempts. Re-merging is not performed for files already marked as resolved. Use ``--all/-a`` to select all unresolved files. ``--tool`` can be used to specify the merge tool used for the given files. It overrides the HGMERGE environment variable and your configuration files. Previous file contents are saved with a ``.orig`` suffix. - HGUSER (deprecated) - configuration files from the HGRCPATH - EMAIL - interactive prompt - LOGNAME (with ``@hostname`` appended) - Mercurial [hg] - CVS [cvs] - Darcs [darcs] - git [git] - Subversion [svn] - Monotone [mtn] - GNU Arch [gnuarch] - Bazaar [bzr] - Perforce [p4] - Mercurial [hg] - Subversion [svn] (history on branches is not preserved) - Modified and unmodified tracked files - Ignored files (unless --all is specified) - New files added to the repository (with :hg:`add`) - Otherwise, the value from the "histedit.defaultrev" config option is used as a revset to select the base revision when ANCESTOR is not specified. The first revision returned by the revset is used. By default, this selects the editable history that is unique to the ancestry of the working directory. - Specify ANCESTOR directly - Unknown files: files marked with "?" by :hg:`status` - Empty directories: in fact Mercurial ignores directories unless they contain files under source control management - Use --outgoing -- it will be the first linear changeset not included in destination. (See :hg:`help config.paths.default-push`) - ``good``, ``bad``, ``skip``: csets explicitly marked as good/bad/skip - ``goods``, ``bads`` : csets topologically good/bad - ``range`` : csets taking part in the bisection - ``pruned`` : csets that are goods, bads or skipped - ``untested`` : csets whose fate is yet unknown - ``ignored`` : csets ignored due to DAG topology - ``current`` : the cset currently being bisected - ``rev`` for the revision number, - ``branch`` for the branch name, - ``desc`` for the commit message (description), - ``user`` for user name (``author`` can be used as an alias), - ``date`` for the commit date - ``topo`` for a reverse topographical sort - ``status(3, 7, added())`` - matches files added from "3" to "7" - `drop` to omit changeset - `edit` to edit this changeset (preserving date) - `fold` to combine it with the preceding changeset (using the later date) - `mess` to reword the changeset commit message - `pick` to [re]order a changeset - `roll` like fold, but discarding this commit's description and date - if it's a directory, all files ending with .rc are added - otherwise, the file itself will be added - size('1k') - files from 1024 to 2047 bytes - size('< 20k') - files less than 20480 bytes - size('>= .5MB') - files at least 524288 bytes - size('4k - 1MB') - files from 4096 bytes to 1048576 bytes - transplant all changes up to REV on top of your current revision:: --branchsort convert from parent to child revision when possible, which means branches are usually converted one after the other. It generates more compact repositories. --closesort try to move closed revisions as close as possible to parent branches, only supported by Mercurial sources. --datesort sort revisions by date. Converted repositories have good-looking changelogs but are often an order of magnitude larger than the same ones generated by --branchsort. --source/-s specifies another repository to use for selecting changesets, just as if it temporarily had been pulled. If --branch/-b is specified, these revisions will be used as heads when deciding which changesets to transplant, just as if only these revisions had been pulled. If --all/-a is specified, all the revisions up to the heads specified with --branch will be transplanted. --sourcesort try to preserve source revisions order, only supported by Mercurial sources. -e/--edit, -m/--message or -l/--logfile set the patch header as well as the commit message. If none is specified, the header is empty and the commit message is '[mq]: PATCH'. -u/--user and -d/--date can be used to set the (given) user and date, respectively. -U/--currentuser and -D/--currentdate set user to current user and date to current date. 1. ``us-ascii``: always first, regardless of settings 2. ``email.charsets``: in order given by user 3. ``ui.fallbackencoding``: if not in email.charsets 4. ``$HGENCODING``: if not in email.charsets 5. ``utf-8``: always last, regardless of settings :``%%``: literal "%" character :``%H``: changeset hash (40 hexadecimal digits) :``%N``: number of patches being generated :``%R``: changeset revision number :``%b``: basename of the exporting repository :``%h``: short-form changeset hash (12 hexadecimal digits) :``%m``: first line of the commit message (only alphanumeric characters) :``%n``: zero-padded sequence number, starting at 1 :``%r``: zero-padded changeset revision number :``\``: literal "\" character :``%%``: literal "%" character :``%s``: basename of file being printed :``%d``: dirname of file being printed, or '.' if in repository root :``%p``: root-relative path name of file being printed :``%H``: changeset hash (40 hexadecimal digits) :``%R``: changeset revision number :``%h``: short-form changeset hash (12 hexadecimal digits) :``%r``: zero-padded changeset revision number :``%b``: basename of the exporting repository :``\``: literal "\" character :``files``: a directory full of files (default) :``tar``: tar archive, uncompressed :``tbz2``: tar archive, compressed using bzip2 :``tgz``: tar archive, compressed using gzip :``uzip``: zip archive, uncompressed :``zip``: zip archive, compressed using deflate :convert.cvsps.cache: Set to False to disable remote log caching, for testing and debugging purposes. Default is True. :convert.cvsps.fuzz: Specify the maximum time (in seconds) that is allowed between commits with identical user and log message in a single changeset. When very large files were checked in as part of a changeset then the default may not be long enough. The default is 60. :convert.cvsps.mergefrom: Specify a regular expression to which commit log messages are matched. If a match occurs, then the conversion process will add the most recent revision on the branch indicated in the regex as the second parent of the changeset. Default is ``{{mergefrombranch ([-\w]+)}}`` :convert.cvsps.mergeto: Specify a regular expression to which commit log messages are matched. If a match occurs, then the conversion process will insert a dummy revision merging the branch on which this log message occurs to the branch indicated in the regex. Default is ``{{mergetobranch ([-\w]+)}}`` :convert.git.findcopiesharder: while detecting copies, look at all files in the working copy instead of just changed ones. This is very expensive for large projects, and is only effective when ``convert.git.similarity`` is greater than 0. The default is False. :convert.git.similarity: specify how similar files modified in a commit must be to be imported as renames or copies, as a percentage between ``0`` (disabled) and ``100`` (files must be identical). For example, ``90`` means that a delete/add pair will be imported as a rename if more than 90% of the file hasn't changed. The default is ``50``. :convert.git.skipsubmodules: does not convert root level .gitmodules files or files with 160000 mode indicating a submodule. Default is False. :convert.hg.clonebranches: dispatch source branches in separate clones. The default is False. :convert.hg.ignoreerrors: ignore integrity errors when reading. Use it to fix Mercurial repositories with missing revlogs, by converting from and to Mercurial. Default is False. :convert.hg.revs: revset specifying the source revisions to convert. :convert.hg.saverev: store original revision ID in changeset (forces target IDs to change). It takes a boolean argument and defaults to False. :convert.hg.sourcename: records the given string as a 'convert_source' extra value on each commit made in the target repository. The default is None. :convert.hg.startrev: specify the initial Mercurial revision. The default is 0. :convert.hg.tagsbranch: branch name for tag revisions, defaults to ``default``. :convert.hg.usebranchnames: preserve branch names. The default is True. :convert.localtimezone: use local time (as determined by the TZ environment variable) for changeset date/times. The default is False (use UTC). :convert.p4.encoding: specify the encoding to use when decoding standard output of the Perforce command line tool. The default is default system encoding. :convert.p4.startrev: specify initial Perforce revision (a Perforce changelist number). :convert.skiptags: does not convert tags from the source repo to the target repo. The default is False. :convert.svn.branches: specify the directory containing branches. The default is ``branches``. :convert.svn.startrev: specify start Subversion revision number. The default is 0. :convert.svn.tags: specify the directory containing tags. The default is ``tags``. :convert.svn.trunk: specify the name of the trunk branch. The default is ``trunk``. :hooks.cvschangesets: Specify a Python function to be called after the changesets are calculated from the CVS log. The function is passed a list with the changeset entries, and can modify the changesets in-place, or add or delete them. :hooks.cvslog: Specify a Python function to be called at the end of gathering the CVS log. The function is passed a list with the log entries, and can modify the entries in-place, or add or delete them. = []... . = . = = A URL path argument is the changeset identifier to show. See ``hg help revisions`` for possible values. If not defined, the ``tip`` changeset will be shown. A bookmark named '@' has the special property that :hg:`clone` will check it out by default if it exists. Accepted destination formats [identifiers]: Accepted source formats [identifiers]: Accepts 0 or more changesets. Will return empty list when passed no args. Greatest common ancestor of a single changeset is that changeset. Accepts a revision range or the -a/--applied option. If --applied is specified, all applied mq revisions are removed from mq control. Otherwise, the given revisions must be at the base of the stack of applied patches. Add all new files and remove all missing files from the repository. After a successful unshelve, the shelved changes are stored in a backup directory. Only the N most recent backups are kept. N defaults to 10 but can be overridden using the ``shelve.maxbackups`` configuration option. After running this command you will need to make sure that largefiles is enabled anywhere you intend to push the new repository. All Destinations ################ All destination types accept the following options: All known branches are contained in the output, even closed branches. Allowed values are: ``tls1.0``, ``tls1.1``, ``tls1.2``. Alternatively you can specify -c/--change with a revision to see the changes in that changeset relative to its first parent. An additional "debugcvsps" Mercurial command allows the builtin changeset merging code to be run without doing a conversion. Its parameters and output are similar to that of cvsps 2.1. Please see the command help for more details. An existing changeset may be placed under mq control with -r/--rev (e.g. qimport --rev . -n patch will place the current revision under mq control). With -g/--git, patches imported with --rev will use the git diff format. See the diffs help topic for information on why this is important for preserving rename/copy information and permission changes. Use :hg:`qfinish` to remove changesets from mq control. Any stripped changesets are stored in ``.hg/strip-backup`` as a bundle (see :hg:`help bundle` and :hg:`help unbundle`). They can be restored by running :hg:`unbundle .hg/strip-backup/BUNDLE`, where BUNDLE is the bundle file created by the strip. Note that the local revision numbers will in general be different after the restore. Apply one or more bundle files generated by :hg:`bundle`. Applying bundles preserves all changeset contents including permissions, copy/rename information, and revision history. As a shortcut, you can also use the revision argument to mark a revision as good or bad without checking it out first. Be careful with purge, as you could irreversibly delete some files you forgot to add to the repository. If you only want to print the list of files that this program would delete, use the --print option. Because this handler can only show information for directories, it is recommended to use the ``file`` handler instead, as it can handle both directories and files. Before using this command, you will need to enable email in your hgrc. See the [email] section in hgrc(5) for details. Bookmarks are labels on changesets to help track lines of development. Bookmarks are unversioned and can be moved, renamed and deleted. Deleting or moving a bookmark has no effect on the associated changesets. Bookmarks can be pushed and pulled between repositories (see :hg:`help push` and :hg:`help pull`). If a shared bookmark has diverged, a new 'divergent bookmark' of the form 'name@path' will be created. Using :hg:`merge` will resolve the divergence. Bookmarks can be renamed, copied and deleted. Bookmarks are local, unless they are explicitly pushed or pulled between repositories. Pushing and pulling bookmarks allow you to collaborate with others on a branch without creating a named branch. Branches may be created when changes are pulled from or pushed to a remote repository, since new heads may be created by these operations. Note that the term branch can also be used informally to describe a development process in which certain development is done independently of other development. This is sometimes done explicitly with a named branch, but it can also be done locally, using bookmarks or clones and anonymous branches. Bundle must be specified by the -R option. But it will leave untouched: 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. By default this command prints revision number and changeset id, tags, non-trivial parents, user, date and time, and a summary for each commit. When the -v/--verbose switch is used, the list of changed files and full commit message are shown. By default, abort if the working directory contains uncommitted changes. With --keep-changes, abort only if the uncommitted files overlap with patched files. With -f/--force, backup and discard changes made to such files. By default, abort if the working directory contains uncommitted changes. With --keep-changes, abort only if the uncommitted files overlap with patched files. With -f/--force, backup and patch over uncommitted changes. By default, all sources except Mercurial will use --branchsort. Mercurial uses --sourcesort to preserve original revision numbers order. Sort modes have the following effects: By default, ancestors of 'startrev' are returned. If 'descend' is True, descendants of 'startrev' are returned though renames are (currently) not followed in this direction. 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. By default, grep prints the most recent revision number for each file in which it finds a match. To get it to print every revision that contains a change in match status ("-" for a match that becomes a non-match, or "+" for a non-match that becomes a match), use the --all flag. By default, push will not allow creation of new heads at the destination, since multiple heads would make it unclear which head to use. In this situation, it is recommended to pull and merge before pushing. By default, the highest version of TLS supported by both client and server is used. By default, the revision used is the parent of the working directory; use -r/--rev to specify a different revision. By default, the server logs accesses to stdout and errors to stderr. Use the -A/--accesslog and -E/--errorlog options to log to files. By default, this command copies the contents of files as they exist in the working directory. If invoked with -A/--after, the operation is recorded, but no copying is performed. By default, this command searches all directories in the working directory. To search just the current directory and its subdirectories, use "--include .". CVS Source ########## CVS source will use a sandbox (i.e. a checked-out copy) from CVS to indicate the starting point of what will be converted. Direct access to the repository files is not needed, unless of course the repository is ``:local:``. The conversion uses the top level directory in the sandbox to find the CVS repository, and then uses CVS rlog commands to find files to convert. This means that unless a filemap is given, all files under the starting directory will be converted, and that any directory reorganization in the CVS sandbox is ignored. Changeset 3b16791d6642 in repository-name. http://my-project.org/hg/repository-name/rev/3b16791d6642 Changeset commit comment. Bug 1234. Changesets that are ancestors of the current revision, that have already been grafted, or that are merges will be skipped. Closed heads can be re-opened by committing new changeset as the child of the changeset that marks a head as closed. Comment lines start with ``#``. A specified path matches if it equals the full relative name of a file or one of its parent directories. The ``include`` or ``exclude`` directive with the longest matching path applies, so line order does not matter. Commit changes to the given files into the repository. Unlike a centralized SCM, this operation is a local operation. See :hg:`push` for a way to actively distribute your changes. Configuration Options: Consider using the graft command if everything is inside the same repository - it will use merges and will usually give a better result. Use the rebase extension if the changesets are unpublished and you want to move them instead of copying them. Convert repository SOURCE to a new repository DEST, identical to SOURCE except that certain files will be converted as largefiles: specifically, any file that matches any PATTERN *or* whose size is above the minimum size threshold is converted as a largefile. The size used to determine whether or not to track a file as a largefile is the size of the first version of the file. The minimum size can be specified either with --size or in configuration as ``largefiles.size``. Copy the store data to the repo and remove the sharedpath data. Create a copy of an existing repository in a new directory. Creating or updating to a bookmark causes it to be marked as 'active'. The active bookmark is indicated with a '*'. When a commit is made, the active bookmark will advance to the new commit. A plain :hg:`update` will also advance an active bookmark, if possible. Updating away from a bookmark will cause it to be deactivated. Defaults to showing the hash, tags, branches, bookmarks, author, and the first line of the commit description. Delete files not known to Mercurial. This is useful to test local and uncommitted changes in an otherwise-clean source tree. Differences between files are shown using the unified diff format. Do not attempt any read operations on this repository while the command is running. (Both repositories will be locked against writes.) Each member added to an archive file has a directory prefix prepended. Use -p/--prefix to specify a format string for the prefix. The default is the basename of the archive, with suffixes removed. 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. Each shelved change has a name that makes it easier to find later. The name of a shelved change defaults to being based on the active bookmark, or if there is no active bookmark, the current named branch. To specify a different name, use ``--name``. Empty lines and lines starting with a ``#`` are ignored. Enabled by default. Equivalent options set via command line flags or environment variables are not overridden. Example: Example: "Did you see my correction in the diff?" Example: "I'm going to branch at X." Example: "I'm going to check out changeset X." Example: "I'm going to clone the repository." Example: "I'm using checkout X." Example: "I've pushed an update." Example: "I've sent you my patch." Example: "If you diff with changeset X, you will see what I mean." Example: "Is the bug fixed in your recent commit?" Example: "Is your clone up to date?" Example: "The experimental branch." Example: "You should commit those changes now." Example: "You should update." Example: "You will need to patch that revision." Examples:: Explicitly setting this environment variable is a good practice to guarantee consistent results. "utf-8" is a good choice on UNIX-like environments. Extend the current configuration by specifying maps as arguments and using -f/--rcfile to source an external hgrc file. File history is shown without following rename or copy history of files. Use -f/--follow with a filename to follow history across renames and copies. --follow without a filename will only show ancestors of the starting revision. Files that changed between either parent are marked as changed for the next commit and a commit must be performed before any further updates to the repository are allowed. The next commit will have two parents. Finally, the patch itself, as generated by :hg:`export`. Finishes the specified revisions (corresponding to applied patches) by moving them out of mq control into regular repository history. For URLs of the form ``/log/{revision}/{file}``, the history for a specific file will be shown. This form is equivalent to the ``filelog`` handler. For URLs of the form ``/log/{revision}``, a list of changesets starting at the specified changeset identifier is shown. If ``{revision}`` is not defined, the default is ``tip``. This form is equivalent to the ``changelog`` handler. For a faster but less accurate result, consider using ``filelog()`` instead. For a regular expression or case sensitive search of these fields, use ``grep(regex)``. For each element in HGRCPATH: For non-searches, the ``changelog`` template will be rendered. For performance reasons, visits only revisions mentioned in the file-level filelog, rather than filtering through all changesets (much faster, but doesn't include deletes or duplicate changes). For a slower, more accurate result, use ``file()``. Generate a bundle file containing data to be transferred to another repository. Git Source ########## Given a topic, extension, or command name, print help for that topic. Guards control whether a patch can be pushed. A patch with no guards is always pushed. A patch with a positive guard ("+foo") is pushed only if the :hg:`qselect` command has activated it. A patch with a negative guard ("-foo") is never pushed if the :hg:`qselect` command has activated it. Heads are where development generally takes place and are the usual targets for update and merge operations. Here are the ways to select changesets: Hg debugcvsps reads the CVS rlog for current directory (or any named directory) in the CVS repository, and converts the log to a series of changesets based on matching commit log entries and dates. Host *.mylocalnetwork.example.com Compression no Host * Compression yes If --exact is specified, import will set the working directory to the parent of each patch before applying it, and will abort if the resulting changeset has a different ID than the one recorded in the patch. This will guard against various ways that portable patch formats and mail systems might fail to transfer Mercurial data or metadata. See :hg:`bundle` for lossless transmission. If --force is specified, revisions will be grafted even if they are already ancestors of, or have been grafted to, the destination. This is useful when the revisions have since been backed out. If --log is specified, log messages will have a comment appended of the form:: If -B/--bookmark is used, the specified bookmarked revision, its ancestors, and the bookmark will be pushed to the remote repository. Specifying ``.`` is equivalent to specifying the active bookmark's name. If -c/--closed is specified, also show branch heads marked closed (see :hg:`commit --close-branch`). If -e/--edit is specified, Mercurial will start your configured editor for you to enter a message. In case qrefresh fails, you will find a backup of your message in ``.hg/last-message.txt``. If -r/--rev is used, the specified revision and all its ancestors will be pushed to the remote repository. If -s/--short is specified, files currently included in the patch will be refreshed just like matched files and remain in the patch. If -t/--topo is specified, named branch mechanics will be ignored and only topological heads (changesets with no children) will be shown. If REV is the parent of the working directory, then this new changeset is committed automatically (unless --no-commit is specified). If SOURCE is omitted, the 'default' path will be used. See :hg:`help urls` for more information. If STARTREV is specified, only those heads that are descendants of STARTREV will be displayed. If ``REVMAP`` isn't given, it will be put in a default location (``/.hg/shamap`` by default). The ``REVMAP`` is a simple text file that maps each source commit ID to the destination ID for that revision, like so:: If ``path`` is a directory, information about the entries in that directory will be rendered. This form is equivalent to the ``manifest`` handler. If ``path`` is a file, information about that file will be shown via the ``filerevision`` template. If ``path`` is not defined, information about the root directory will be rendered. If ``revision`` is absent, the ``rev`` query string argument may be defined. This will perform a search for changesets. If a changeset application fails, you can fix the merge by hand and then resume where you left off by calling :hg:`transplant --continue/-c`. If a fingerprint is specified, the CA chain is not validated for this host and Mercurial will require the remote certificate to match one of the fingerprints specified. This means if the server updates its certificate, Mercurial will abort until a new fingerprint is defined. This can provide stronger security than traditional CA-based validation at the expense of convenience. If a graft merge results in conflicts, the graft process is interrupted so that the current merge can be manually resolved. Once all conflicts are addressed, the graft process can be continued with the -c/--continue option. If a list of files is omitted, all changes reported by :hg:`status` will be candidates for recording. If a list of files is omitted, all changes reported by :hg:`status` will be committed. If a parent of the working directory is stripped, then the working directory will automatically be updated to the most recent available ancestor of the stripped parent after the operation completes. If a rebase is interrupted to manually resolve a conflict, it can be continued with --continue/-c or aborted with --abort/-a. If a shelved change is applied successfully, the bundle that contains the shelved changes is moved to a backup location (.hg/shelve-backup). If any file patterns are provided, the refreshed patch will contain only the modifications that match those patterns; the remaining modifications will remain in the working directory. If any of specified revisions is not present in the local repository, the query is normally aborted. But this predicate allows the query to continue even in such cases. If bare shelved change(when no files are specified, without interactive, include and exclude option) was done on newly created branch it would restore branch information to the working directory. If defined, only certificates provided by this file will be used: ``web.cacerts`` and any system/default certificates will not be used. If directories are given on the command line, only files in these directories are considered. If no FILEs are specified (and -f/--follow isn't set), all files in the repository are searched, including those that don't exist in the current branch or have been deleted in a prior changeset. If no commit message is specified, Mercurial starts your configured editor where you can enter a message. In case your commit fails, you will find a backup of your message in ``.hg/last-message.txt``. If no destination directory name is specified, it defaults to the basename of the source with ``-hg`` appended. If the destination repository doesn't exist, it will be created. If no destination directory name is specified, it defaults to the basename of the source. If no directory is given, the current directory is used. If no files are given to match, this command prints the names of all files under Mercurial control. If no merges or revisions are provided, :hg:`transplant` will start an interactive changeset browser. If no names are given, add all files to the repository (except files matching ``.hgignore``). If no patterns are given to match, this command prints the names of all files under Mercurial control in the working directory. If no revision is given, all revisions will be converted. Otherwise, convert will only import up to the named revision (given in a format understood by the source). If no revision is given, the parent of the working directory is used. If no revision is given, the parent of the working directory is used, or tip if no revision is checked out. If no revision is specified, the working directory's parent is a head revision, and the current branch contains exactly one other head, the other head is merged with by default. Otherwise, an explicit revision with which to merge with must be provided. If no revision range is specified, the default is ``tip:0`` unless --follow is set, in which case the working directory parent is used as the starting revision. If one or more REVs are given, only open branch heads on the branches associated with the specified changesets are shown. This means that you can use :hg:`heads .` to see the heads on the currently checked-out branch. If one revision is given, it is used as the base revision. If two revisions are given, the differences between them are shown. The --change option can also be used as a shortcut to list the changed files of a revision from its first parent. If option --all is specified, the list of all files from all revisions is printed. This includes deleted and renamed files. If some linkrev points to revisions filtered by the current repoview, we'll work around it to return a non-filtered value. If source is local, destination will have no patches applied. If source is remote, this command can not check if patches are applied in source, so cannot guarantee that patches are not applied in destination. If you clone remote repository, be sure before that it has no patches applied. If the URL path arguments are omitted, information about the root directory for the ``tip`` changeset will be shown. If the changeset is not a descendant or ancestor of the working directory's parent and there are uncommitted changes, the update is aborted. With the -c/--check option, the working directory is checked for uncommitted changes; if none are found, the working directory is updated to the specified changeset. If the file doesn't exist, it's automatically created. It's updated on each commit copied, so :hg:`convert` can be interrupted and can be run repeatedly to copy new commits. If the imported patch was generated by :hg:`export`, user and description from patch override values from message headers and body. Values given on command line with -m/--message and -u/--user override these. If the optional ``revision`` URL argument is absent, information about all changesets starting at ``tip`` will be rendered. If the ``revision`` argument is present, changesets will be shown starting from the specified revision. If the pulled changes add a new branch head, the head is automatically merged, and the result of the merge is committed. Otherwise, the working directory is updated to include the new changes. If the source repository has a bookmark called '@' set, that revision will be checked out in the new repository by default. If using the text interface (see :hg:`help config`), you will be prompted for whether to record changes to each modified file, and for files with multiple changes, for each change to use. For each query, the following responses are possible:: If you are committing the result of a merge, do not provide any filenames or -I/-X filters. If you don't specify a destination changeset (``-d/--dest``), rebase will use the same logic as :hg:`merge` to pick a destination. if the current branch contains exactly one other head, the other head is merged with by default. Otherwise, an explicit revision with which to merge with must be provided. (destination changeset is not modified by rebasing, but new changesets are added as its descendants.) If you have just made a commit, that commit will be the tip. If you have just pulled changes from another repository, the tip of that repository becomes the current tip. The "tip" tag is special and cannot be renamed or assigned to a different changeset. If you include --file, --user, or --date, the revision number is suppressed unless you also include --number. If you need to use a tool to automate merge/conflict decisions, you can specify one with ``--tool``, see :hg:`help merge-tools`. As a caveat: the tool will not be used to mediate when a file was deleted, there is no hook presently available for this. If you supply a command, it will be used for automatic bisection. The environment variable HG_NODE will contain the ID of the changeset being tested. The exit status of the command will be used to mark revisions as good or bad: status 0 means good, 125 means to skip the revision, 127 (command not found) will abort the bisection, and any other non-zero exit status means the revision is bad. If you use non-ASCII characters in names for tags, branches, bookmarks, authors, and/or commit descriptions, you must pay attention to encodings of managed files. At template expansion, non-ASCII characters use the encoding specified by the ``--encoding`` global option, ``HGENCODING`` or other environment variables that govern your locale. If the encoding of the merge markers is different from the encoding of the merged files, serious problems may occur. If you want to feed the output of this command into the "xargs" command, use the -0 option to both this command and "xargs". This will avoid the problem of "xargs" treating single filenames that contain whitespace as multiple filenames. If you want to revert just one file to an older revision, use :hg:`revert [-r REV] NAME`. Import a list of patches and commit them individually (unless --no-commit is specified). Import first applies changes to the working directory (unless --bypass is specified), import will abort if there are outstanding changes. In bare shelve (when no files are specified, without interactive, include and exclude option), shelving remembers information if the working directory was on newly created branch, in other words working directory was on different branch than its first parent. In this situation unshelving restores branch information to the working directory. In case email sending fails, you will find a backup of your series introductory message in ``.hg/last-email.txt``. Info about the ``path`` given as a URL parameter will be rendered. Information about the latest changesets, bookmarks, tags, and branches is captured by this handler. Information rendered by this handler can be used to create visual representations of repository topology. Initialize a new repository and working directory that shares its history (and optionally bookmarks) with another repository. Initialize a new repository in the given directory. If the given directory does not exist, it will be created. It is highly recommended for machines to set this variable when invoking ``hg`` processes. It is not possible to amend public changesets (see :hg:`help phases`) or changesets that have children. It is possible to map alternate email addresses to a main address by providing a file using the following format:: It is possible to specify a patch tool together with extra arguments. For example, setting this option to ``patch --merge`` will use the ``patch`` program with its 2-way merge option. It is possible to specify an ``ssh://`` URL as the destination. See :hg:`help urls` for more information. It is possible to use external patch programs to perform the patch by setting the ``ui.patch`` configuration option. For the default internal tool, the fuzz can also be configured via ``patch.fuzz``. See :hg:`help config` for more information about configuration files and how to use these options. Labels are exposed as a template keyword and can be used to customize output. e.g. the ``index`` template can group or filter repositories by labels and the ``summary`` template can display additional content if a specific label is present. Line range corresponds to 'file' content at 'startrev' and should hence be consistent with file size. If startrev is not specified, working directory's parent is used. List changes in files, showing the revision id responsible for each line. List the repository's named branches, indicating which ones are inactive. If -c/--closed is specified, also list branches which have been marked closed (see :hg:`commit --close-branch`). List which files in the working directory are matched by the [keyword] configuration patterns. Mark dest as copies of sources; mark sources for deletion. If dest is a directory, copies are put in that directory. If dest is a file, there can only be one source. Mark dest as having copies of source files. If dest is a directory, copies are put in that directory. If dest is a file, the source must be a single file. Mark the specified files so they will no longer be tracked after the next commit. Mercurial Destination ##################### Mercurial Source ################ Merge changesets may be transplanted directly by specifying the proper parent changeset by calling :hg:`transplant --parent`. Merges with unresolved conflicts are often the result of non-interactive merging using the ``internal:merge`` configuration setting, or a command-line merge tool like ``diff3``. The resolve command is used to manage the files involved in a merge, after :hg:`merge` has been run, and before :hg:`commit` is run (i.e. the working directory must have two parents). See :hg:`help merge-tools` for information on configuring merge tools. Message, user and date are taken from the amended commit unless specified. When a message isn't specified on the command line, the editor will open with the message of the amended commit. Modified files are saved with a .orig suffix before reverting. To disable these backups, use --no-backup. It is possible to store the backup files in a custom directory relative to the root of the repository by setting the ``ui.origbackuppath`` configuration option. Must be run before changing/disabling active keywords. NOTE: this concept is deprecated because it is too implicit. Branches should now be explicitly closed using :hg:`commit --close-branch` when they are no longer needed. Name a particular revision using . Named branches can be thought of as a kind of namespace, dividing the collection of changesets that comprise the repository into a collection of disjoint subsets. A named branch is not necessarily a topological branch. If a new named branch is created from the head of another named branch, or the default branch, but no further changesets are added to that previous branch, then that previous branch will be a branch in name only. No arguments are accepted. No template is used for this handler. Raw, binary content is generated. Nodes printed as an @ character are parents of the working directory. Note: the cookies parser does not handle port numbers on domains. You will need to remove ports from the domain for the cookie to be recognized. This could result in a cookie being disclosed to an unwanted server. Obtain an archive of repository content. Omitting a queue name or specifying -l/--list will show you the registered queues - by default the "normal" patches queue is registered. The currently active queue will be marked with "(active)". Specifying --active will print only the name of the active queue. On Windows, the path can use environment variables with ${ProgramFiles} syntax. Only local paths and ``ssh://`` URLs are supported as destinations. For ``ssh://`` destinations, no working directory or ``.hg/hgrc`` will be created on the remote side. Option -q/--quiet hides untracked (unknown and ignored) files unless explicitly requested with -u/--unknown or -i/--ignored. Option -q/--quiet suppresses all output when searching for NAME and shows only the path names when listing all definitions. Order of outgoing email character sets: Output may be to a file, in which case the name of the file is given using a template string. See :hg:`help templates`. In addition to the common template keywords, the following formatting rules are supported: PATTERN can be any Python (roughly Perl-compatible) regular expression. Patches must not yet be applied. Each patch will be successively applied to the current patch in the order given. If all the patches apply successfully, the current patch will be refreshed with the new cumulative patch, and the folded patches will be deleted. With -k/--keep, the folded patch files will not be removed afterwards. Path names are defined in the [paths] section of your configuration file and in ``/etc/mercurial/hgrc``. If run inside a repository, ``.hg/hgrc`` is used, too. Pattern matching is supported for `name`. See :hg:`help revisions.patterns`. Pattern matching is supported for `name`. See :hg:`help revisions.patterns`. Pattern matching is supported for `namespace`. See :hg:`help revisions.patterns`. Pattern matching is supported for `string`. See :hg:`help revisions.patterns`. Pattern matching is supported for `value`. See :hg:`help revisions.patterns`. Perforce Source ############### Please note that the server does not implement access control. This means that, by default, anybody can read from the server and nobody can write to it by default. Set the ``web.allow-push`` option to ``*`` to allow everybody to push to the server. You should use a real web server if you need to authenticate users. Please see :hg:`help urls` for important details about ``ssh://`` URLs. If DESTINATION is omitted, a default path will be used. Please see https://mercurial-scm.org/wiki/RepositoryCorruption for more information about recovery from corruption of the repository. Please use :hg:`commit --amend` instead of rollback to correct mistakes in the last commit. Please use :hg:`log` instead:: Prepare a new changeset with the effect of REV undone in the current working directory. If no conflicts were encountered, it will be committed immediately. Print a list of version controlled files for the given revision. If no revision is given, the first parent of the working directory is used, or the null revision if no revision is checked out. Print a revision history alongside a revision graph drawn with ASCII characters. Print a summary identifying the repository state at REV using one or two parent hash identifiers, followed by a "+" if the working directory has uncommitted changes, the branch name (if not default), a list of tags, and a list of bookmarks. Print files under Mercurial control in the working directory or specified revision for given files (excluding removed files). Files can be specified as filenames or filesets. Print files under Mercurial control in the working directory whose names match the given patterns. Print the changeset header and diffs for one or more revisions. If no revision is given, the parent of the working directory is used. Print the children of the working directory's revisions. If a revision is given via -r/--rev, the children of that revision will be printed. If a file argument is given, revision in which the file was last changed (after the working directory revision or the argument to --rev if given) is printed. Print the revision history of the specified files or the entire project. Print the root directory of the current repository. Print the specified files as they were at the given revision. If no revision is given, the parent of the working directory is used. Print the working directory's parent revisions. If a revision is given via -r/--rev, the parent of that revision will be printed. If a file argument is given, the revision in which the file was last changed (before the working directory revision or the argument to --rev if given) is printed. Published commits cannot be rebased (see :hg:`help phases`). To copy commits, see :hg:`help graft`. Pull changes from a remote repository to a local one. Pull largefiles that are referenced from local changesets but missing locally, pulling from a remote repository to the local cache. Push changesets from the local repository to the specified destination. Rebase uses repeated merging to graft changesets from one part of history (the source) onto another (the destination). This can be useful for linearizing *local* changes relative to a master development tree. Rebase will destroy original changesets unless you use ``--keep``. It will also move your bookmarks (even if you do). Recover from an interrupted commit or pull. Regular revision fields are ``description``, ``author``, ``branch``, ``date``, ``files``, ``phase``, ``parents``, ``substate``, ``user`` and ``diff``. Note that ``author`` and ``user`` are synonyms. ``diff`` refers to the contents of the revision. Two revisions matching their ``diff`` will also match their ``files``. Render help documentation. Repositories with this on-disk format require Mercurial version 0.9.4. Repositories with this on-disk format require Mercurial version 1.1. Repositories with this on-disk format require Mercurial version 1.7. Repositories with this on-disk format require Mercurial version 1.9. Return 0 on success. Return Values: Returns 0 if a match is found, 1 otherwise. Returns 0 if a match is found, 1 otherwise. Returns 0 if all files are successfully added. Returns 0 if import succeeded. Returns 0 if matching heads are found, 1 if not. Returns 0 if push was successful, 1 if nothing to push. Returns 0 if successful, 1 if nothing to recover or verify fails. Returns 0 if successful. Returns 0 if there are incoming changes, 1 otherwise. Returns 0 if there are outgoing changes, 1 otherwise. Returns 0 on success, 1 if NAME does not exist. Returns 0 on success, 1 if an update had unresolved files. Returns 0 on success, 1 if an update has unresolved files. Returns 0 on success, 1 if any files fail a resolve attempt. Returns 0 on success, 1 if any warnings encountered. Returns 0 on success, 1 if errors are encountered. Returns 0 on success, 1 if no changes found. Returns 0 on success, 1 if no rollback data is available. Returns 0 on success, 1 if nothing changed. Returns 0 on success, 1 if nothing to backout or there are unresolved files. Returns 0 on success, 1 if nothing to rebase or there are unresolved conflicts. Returns 0 on success, 1 if some phases could not be changed. Returns 0 on success, 1 if there are unresolved files. Returns 0 on success, 1 if user intervention is required (not only for intentional "edit" command, but also for resolving unexpected conflicts). Returns 0 on success, 1 on partial success (see --partial). Returns 0 on success. Returns 0 on success. Returns 0 on successful completion. Returns 0 on successful creation of a new patch. Returns 0. Run after (re)enabling keyword expansion. Schedule files to be version controlled and added to the repository. Schedule the indicated files for removal from the current branch. Search revision history for a regular expression in the specified files or the entire project. See :hg:`help backout` for a way to reverse the effect of an earlier changeset. See :hg:`help config` for more information about config files. See :hg:`help dates` for a list of formats valid for -d/--date. See :hg:`help dates` for a list of formats valid for -d/--date. See :hg:`help files` for a more versatile command. See :hg:`help keyword` on how to construct patterns both for inclusion and exclusion of files. See :hg:`help log` and :hg:`help revsets.children`. See :hg:`help patterns` and :hg:`help filesets` for more information on specifying file patterns. See :hg:`help qnew` & :hg:`help record` for more information and usage. See :hg:`help resolve` for information on handling file conflicts. See :hg:`help revert` for a way to restore files to the state of another revision. See :hg:`help revisions` for more about specifying and ordering revisions. See :hg:`help revisions` for more about specifying revisions. See :hg:`help templates` for information on templates and filters. See :hg:`help templates` for more about pre-packaged styles and specifying custom templates. The default template used by the log command can be customized via the ``ui.logtemplate`` configuration setting. See :hg:`help urls` for details on specifying URLs. See :hg:`help urls` for more information. See :hg:`log` for generating more information about specific revisions, including full hash identifiers. See :hg:`summary` and :hg:`help revsets` for related information. See pull for details of valid destination formats. See pull for valid source format details. Selected changesets will be applied on top of the current working directory with the log of the original changeset. The changesets are copied and will thus appear twice in the history with different identities. Setting HGPLAINEXCEPT to anything (even an empty string) will enable plain mode. Shelving takes files that "hg status" reports as not clean, saves the modifications to a bundle (a shelved change), and reverts the files so that their state in the working directory becomes clean. Show a comparison between the old and new versions of a file from changes made on a particular revision. Show a summary of repository state. Show basic information about a set of changesets. Show changeset information for each line in a file. Show changesets not found in the specified destination repository or the default push location. These are the changesets that would be pushed if a push was requested. Show current, custom, or default keyword template maps and their expansions. Show definition of symbolic path name NAME. If no name is given, show definition of all available names. Show differences between revisions for the specified files, using an external program. The default program used is diff, with default options "-Npru". Show differences between revisions for the specified files, using the following program:: Show differences between revisions for the specified files. Show how a file changed in a particular commit. Show information about a directory or file in the repository. Show information about a directory. Show information about a single changeset. Show information about bookmarks. Show information about branches. Show information about multiple changesets. Show information about tags. Show information about the graphical topology of the repository. Show information about the history of a file in the repository. Show new changesets found in the specified path/URL or the default pull location. These are the changesets that would have been pulled by :hg:`pull` at the time you issued this command. Show repository or file history. Show status of files in the repository. If names are given, only files that match are shown. Files that are clean or ignored or the source of a copy/move operation, are not listed unless -c/--clean, -i/--ignored, -C/--copies or -A/--all are given. Unless options described with "show only ..." are given, the options -mardu are used. Shows a diff which includes the current patch as well as any changes which have been made in the working directory since the last refresh (thus showing what the current patch would become after a qrefresh). Similarly, passing --rev to "hg clone" will fail to use any hardlinks, falling back to a complete copy of the source repository. Since tag names have priority over branch names during revision lookup, using an existing branch name as a tag name is discouraged. Since you can restore a shelved change on top of an arbitrary commit, it is possible that unshelving will result in a conflict between your changes and the commits you are unshelving onto. If this occurs, you must resolve the conflict, then use ``--continue`` to complete the unshelve operation. (The bundle will not be moved until you successfully complete the unshelve.) Some changesets may be dropped if they do not contribute changes (e.g. merges from the destination branch). Source history can be retrieved starting at a specific revision, instead of being integrally converted. Only single branch conversions are supported. Source patch repository is looked for in /.hg/patches by default. Use -p to change. Special fields are ``summary`` and ``metadata``: ``summary`` matches the first line of the description. ``metadata`` is equivalent to matching ``description user date`` (i.e. it matches the main metadata fields). Specifying a path to a repository root or Mercurial bundle will cause lookup to operate on that repository/bundle. Specifying bookmark as '.' to -m or -d options is equivalent to specifying the active bookmark's name. Specifying bookmark as ``.`` is equivalent to specifying the active bookmark's name. Start a local HTTP repository browser and pull server. You can use this for ad-hoc sharing and browsing of repositories. It is recommended to use a real web server to serve a repository for longer periods of time. Statistics are based on the number of changed lines, or alternatively the number of matching revisions if the --changesets option is specified. Strip is not a history-rewriting operation and can be used on changesets in the public phase. But if the stripped changesets have been pushed to a remote repository you will likely pull them again. Subversion Source ################# Subversion source detects classical trunk/branches/tags layouts. By default, the supplied ``svn://repo/path/`` source URL is converted as a single branch. If ``svn://repo/path/trunk`` exists it replaces the default branch. If ``svn://repo/path/branches`` exists, its subdirectories are listed as possible branches. If ``svn://repo/path/tags`` exists, it is looked for tags referencing converted branches. Default ``trunk``, ``branches`` and ``tags`` values can be overridden with following options. Set them to paths relative to the source URL, or leave them blank to disable auto detection. Such a file may be specified with the --aliases option, otherwise a .hgchurn file will be looked for in the working directory root. Aliases will be split from the rightmost "=". Supports switching between different patch queues, as well as creating new patch queues and deleting existing ones. Tag commits are usually made at the head of a branch. If the parent of the working directory is not a branch head, :hg:`tag` aborts; use -f/--force to force the tag commit to be based on a non-head changeset. Tags are used to name particular revisions of the repository and are very useful to compare different revisions, to go back to significant earlier versions or to mark branch points as releases, etc. Changing an existing tag is normally disallowed; use -f/--force to override. The --amend flag can be used to amend the parent of the working directory with a new commit that contains the changes in the parent in addition to those currently reported by :hg:`status`, if there are any. The old commit is stored in a backup bundle in ``.hg/strip-backup`` (see :hg:`help bundle` and :hg:`help unbundle` on how to restore it). The --close-branch flag can be used to mark the current branch head closed. When all heads of a branch are closed, the branch will be considered closed and no longer listed. The --files and --dirs options can be used to direct purge to delete only files, only directories, or both. If neither option is given, both will be deleted. The Mercurial destination will recognize Mercurial subrepositories in the destination directory, and update the .hgsubstate file automatically if the destination subrepositories contain the //.hg/shamap file. Converting a repository with subrepositories requires converting a single repository at a time, from the bottom up. The Mercurial source recognizes the following configuration options, which you can set on the command line with ``--config``: The Perforce (P4) importer can be given a p4 depot path or a client specification as source. It will convert all files in the source to a flat Mercurial repository, ignoring labels, branches and integrations. Note that when a depot path is given you then usually should specify a target directory, because otherwise the target may be named ``...-hg``. The ``bookmarks`` template is rendered. The ``branches`` template is rendered. The ``changeset`` template is rendered. Contents of the ``changesettag``, ``changesetbookmark``, ``filenodelink``, ``filenolink``, and the many templates related to diffs may all be used to produce the output. The ``context`` query string argument can be used to control the lines of context in the diff. The ``fileannotate`` template is rendered. The ``filecomparison`` template is rendered. The ``filediff`` template is rendered. The ``filelog`` template will be rendered. The ``gpg.cmd`` config setting can be used to specify the command to run. A default key can be specified with ``gpg.key``. The ``help`` template will be rendered when requesting help for a topic. ``helptopics`` will be rendered for the index of help topics. The ``include`` directive causes a file, or all files under a directory, to be included in the destination repository. The default if there are no ``include`` statements is to include everything. If there are any ``include`` statements, nothing else is included. The ``exclude`` directive causes files or directories to be omitted. The ``rename`` directive renames a file or directory if it is converted. To rename from a subdirectory into the root of the repository, use ``.`` as the path to rename to. The ``manifest`` template will be rendered for this handler. The ``revcount`` query string argument can be defined to control the maximum number of entries to show. The ``revcount`` query string argument can define the number of changesets to show information for. The ``revcount`` query string argument defines the maximum numbers of changesets to render. The ``summary`` template is rendered. The ``tags`` template is rendered. The ``topo`` sort order cannot be combined with other sort keys. This sort takes one optional argument, ``topo.firstbranch``, which takes a revset that specifies what topographical branches to prioritize in the sort. The archive type is automatically detected based on file extension (to override, use -t/--type). The argument for ``rev`` can be a single revision, a revision set, or a literal keyword to search for in changeset data (equivalent to :hg:`log -k`). The authormap is a simple text file that maps each source commit author to a destination commit author. It is handy for source SCMs that use unix logins to identify authors (e.g.: CVS). One line per author mapping and the line format is:: The branchmap is a file that allows you to rename a branch when it is being brought in from whatever external repository. When used in conjunction with a splicemap, it allows for a powerful combination to help fix even the most badly mismanaged repositories and turn them into nicely structured Mercurial repositories. The branchmap contains lines of the form:: The bundle file can then be transferred using conventional means and applied to another repository with the unbundle or pull command. This is useful when direct push and pull are not available or when exporting an entire repository is undesirable. The codes used to show the status of files are:: The content and type of the archive is defined by a URL path parameter. ``format`` is the file extension of the archive type to be generated. e.g. ``zip`` or ``tar.bz2``. Not all archive types may be allowed by your server configuration. The cookies file is read-only. The current working directory is updated with all changes made in the requested revision since the last common predecessor revision. The default behavior of this command can be customized through configuration. (See :hg:`help patchbomb` for details) The exact name of the destination archive or directory is given using a format string; see :hg:`help export` for details. The file format uses the Mozilla cookies.txt format, which defines cookies on their own lines. Each line contains 7 fields delimited by the tab character (domain, is_domain_cookie, path, is_secure, expires, name, value). For more info, do an Internet search for "Netscape cookies.txt format." The filemap is a file that allows filtering and remapping of files and directories. Each line can contain one of the following directives:: The files will be added to the repository at the next commit. To undo an add before that, see :hg:`forget`. The following algorithms/prefixes are supported: ``sha1``, ``sha256``, ``sha512``. The following keys are defined by Mercurial: The following options are supported: The following options can be set with ``--config``: The following options can be used with ``--config``: The format of the file is as follows:: The header for each folded patch will be concatenated with the current patch header, separated by a line of ``* * *``. The information shown in the changeset header is: author, date, branch name (if non-default), changeset hash, parent(s) and commit comment. The key is the revision ID in the source revision control system whose parents should be modified (same format as a key in .hg/shamap). The values are the revision IDs (in either the source or destination revision control system) that should be used as the new parents for that node. For example, if you have merged "release-1.0" into "trunk", then you should specify the revision on "trunk" as the first parent and the one on the "release-1.0" branch as the second. The keys can be: The location of the source is added to the new repository's ``.hg/hgrc`` file, as the default to be used for future pulls. The optional ``path`` URL parameter controls content to include in the archive. If omitted, every file in the specified revision is present in the archive. If included, only the specified file or contents of the specified directory will be included in the archive. The patch directory must be a nested Mercurial repository, as would be created by :hg:`init --mq`. The patch is inserted into the series after the last applied patch. If no patches have been applied, qimport prepends the patch to the series. The patch will have the same name as its source file unless you give it a new one with -n/--name. The patches must not be applied, and at least one patch is required. Exact patch identifiers must be given. With -k/--keep, the patch files are preserved in the patch directory. The path names ``default`` and ``default-push`` have a special meaning. When performing a push or pull operation, they are used as fallbacks if no location is specified on the command-line. When ``default-push`` is set, it will be used for push and ``default`` will be used for pull; otherwise ``default`` is used as the fallback for both. When cloning a repository, the clone source is written as ``default`` in ``.hg/hgrc``. The pattern without explicit kind like ``glob:`` is expected to be relative to the current directory and match against a file exactly for efficiency. The pattern without explicit kind like ``glob:`` is expected to be relative to the current directory and match against a file or a directory. The queue repository is unversioned by default. If -c/--create-repo is specified, qinit will create a separate nested repository for patches (qinit -c may also be run later to convert an unversioned patch repository into a versioned one). You can use qcommit to commit changes to this queue repository. The resolve command can be used in the following ways: The server certificate or the certificate's certificate authority (CA) must match a certificate from this file or certificate verification will fail and connections to the server will be refused. The splicemap is a file that allows insertion of synthetic history, letting you specify the parents of a revision. This is useful if you want to e.g. give a Subversion merge two parents, or graft two disconnected series of history together. Each entry contains a key, followed by a space, followed by one or two comma-separated values:: The strip command removes the specified changesets and all their descendants. If the working directory has uncommitted changes, the operation is aborted unless the --force flag is supplied, in which case changes will be discarded. The tip revision (usually just called the tip) is the changeset most recently added to the repository (and therefore the most recently changed head). There are a number of ways to select the root changeset: This accepts the same parameters as the ``changelog`` handler. The only difference is the ``shortlog`` template will be rendered instead of the ``changelog`` template. This activates the "stable" guard. mq will skip foo.patch (because it has a negative match) but push bar.patch (because it has a positive match). This can be especially useful if your changes have been applied to an upstream repository, or if you are about to push your changes to upstream. This command accepts an optional name of a shelved change to restore. If none is given, the most recent shelved change is used. This command helps to find changesets which introduce problems. To use, mark the earliest changeset you know exhibits the problem as bad, then mark the latest changeset which is free from the problem as good. Bisect will update your working directory to a revision for testing (unless the -U/--noupdate option is specified). Once you have performed tests, mark the working directory as good or bad, and bisect will either update to another candidate changeset or announce that it has found the bad revision. This command is deprecated, please use :hg:`heads` instead. This command is deprecated, use :hg:`rebase` instead. This command is deprecated. Without -c, it's implied by other relevant commands. With -c, use :hg:`init --mq` instead. This command is deprecated; use :hg:`commit --mq` instead. This command is equivalent to:: This command is intended as a debugging tool for the CVS to Mercurial converter, and can be used as a direct replacement for cvsps. This command is not available when committing a merge. This command is not intended for use on public repositories. Once changes are visible for pull by other users, rolling a transaction back locally is ineffective (someone else may already have pulled the changes). Furthermore, a race is possible with readers of the repository; for example an in-progress pull from the repository may fail if a rollback is performed. This command is useful for discovering when a change was made and by whom. This command lets you edit a linear series of changesets (up to and including the working directory, which should be clean). You can: This command lets you recreate those hardlinks and reclaim that wasted space. This command schedules the files to be removed at the next commit. To undo a remove before that, see :hg:`revert`. To undo added files, see :hg:`forget`. This command should be used with care. There is only one level of rollback, and there is no way to undo a rollback. It will also restore the dirstate at the time of the last transaction, losing any dirstate changes since that time. This command does not alter the working directory. This command takes effect at the next commit. To undo a rename before that, see :hg:`revert`. This command takes effect with the next commit. To undo a copy before that, see :hg:`revert`. This command tries to fix the repository status after an interrupted operation. It should only be necessary when Mercurial suggests it. This command uses Mercurial's merge logic to copy individual changes from other branches without merging branches in the history graph. This is sometimes known as 'backporting' or 'cherry-picking'. By default, graft will copy user, date, and description from the source changesets. This command will display a histogram representing the number of changed lines or revisions, grouped according to the given template. The default template will group changes by author. The --dateformat option may be used to group the results by date instead. This finds all changes from the repository at the specified path or URL and adds them to a local repository (the current one unless -R is specified). By default, this does not update the copy of the project in the working directory. This finds all changes from the repository at the specified path or URL and adds them to the local repository. This generates a brief summary of the working directory state, including parents, branch, commit status, phase and available updates. This handler is registered under both the ``/diff`` and ``/filediff`` paths. ``/diff`` is used in modern code. This handler will render the ``graph`` template. This implies premerge. Therefore, files aren't dumped, if premerge runs successfully. Use :forcedump to forcibly write files out. This is an alias to :hg:`log -G`. This is disabled by default because servers advertising "clone bundles" often do so to reduce server load. If advertised bundles start mass failing and clients automatically fall back to a regular clone, this would add significant and unexpected load to the server since the server is expecting clone operations to be offloaded to pre-generated bundles. Failing fast (the default behavior) ensures clients don't overwhelm the server when "clone bundle" application fails. This is equivalent to passing ``--profile`` on the command line. This is similar to the ``diff`` handler. However, this form features a split or side-by-side diff rather than a unified diff. This lists both regular and local tags. When the -v/--verbose switch is used, a third column "local" is printed for local tags. When the -q/--quiet switch is used, only the tag name is printed. This means that purge will delete the following by default: This only removes files from the current branch, not from the entire project history, and it does not delete them from the working directory. This operation is symmetrical to pull: it is identical to a pull in the destination repository from the current one. This option has no effect if the per-host ``fingerprints`` option is set. This option requires Python 2.7. This option takes precedence over ``verifycertsfile``. This predicate uses ``glob:`` as the default kind of pattern. This repository will be relinked to share space with ORIGIN, which must be on the same local disk. If ORIGIN is omitted, looks for "default-relink", then "default", in [paths]. This setting can be overridden by a ``context`` request parameter to the ``comparison`` command, taking the same values. This setting is for advanced users only. Setting to incorrect values can significantly lower connection security or decrease performance. You have been warned. This web command is roughly equivalent to :hg:`help`. If a ``topic`` is defined, that help topic will be rendered. If not, an index of available help topics will be rendered. This will perform an extensive check of the repository's integrity, validating the hashes and checksums of each entry in the changelog, manifest, and tracked files, as well as the integrity of their crosslinks and indices. To cancel an uncommitted merge (and lose your changes), use :hg:`merge --abort`. To check out a particular version, use -u/--update, or -U/--noupdate to create a clone with no working directory. To create a bundle containing all changesets, use -a/--all (or --base null). Otherwise, hg assumes the destination will have all the nodes you specify with --base parameters. Otherwise, hg will assume the repository has all the nodes in destination, or default-push/default if no destination is specified, where destination is the repository you provide through DEST option. To create a new queue, use -c/--create. The queue is automatically made active, except in the case where there are applied patches from the currently active queue in the repository. Then the queue will only be created and switching will fail. To delete an existing queue, use --delete. You cannot delete the currently active queue. To delete specific shelved changes, use ``--delete``. To delete all shelved changes, use ``--cleanup``. To delete the file from the working directory, see :hg:`remove`. To disable SSL verification temporarily, specify ``--insecure`` from command line. To facilitate version control, distribution, and merging of tags, they are stored as a file named ".hgtags" which is managed similarly to other project files and can be hand-edited if necessary. This also means that tagging creates a new commit. The file ".hg/localtags" is used for local tags (not shared among repositories). To have the server choose a free port number to listen on, specify a port number of 0; in this case, the server will print the port number it uses. To import a patch from standard input, pass - as the patch file. When importing from standard input, a patch name must be specified using the --name flag. To import an existing patch while renaming it:: To match more than one field pass the list of fields to match separated by spaces (e.g. ``author description``). To pull only a subset of changesets, specify one or more revisions identifiers with -r/--rev or branches with -b/--branch. The resulting clone will contain only the specified changesets and their ancestors. These options (or 'clone src#rev dest') imply --pull, even for local source repositories. To read a patch from standard input (stdin), use "-" as the patch name. If a URL is specified, the patch will be downloaded from there. To restore these changes to the working directory, using "hg unshelve"; this will work even if you switch to a different commit. To see a list of existing shelved changes, use the ``--list`` option. For each shelved change, this will print its name, age, and description; use ``--patch`` or ``--stat`` for more details. To select a different program, use the -p/--program option. The program will be passed the names of two directories to compare. To pass additional options to the program, use -o/--option. These will be passed before the names of the directories to compare. To set guards on another patch:: To stop managing a patch and move it into permanent history, use the :hg:`qfinish` command. To undo a forget before the next commit, see :hg:`add`. To undo an uncommitted merge, use :hg:`merge --abort` which will check out a clean copy of the original merge parent, losing all changes. Transactions are used to encapsulate the effects of all commands that create new changesets or propagate existing changesets into a repository. Unfortunately, subsequent pulls into either repository will break hardlinks for any files touched by the new changesets, even if both repositories end up pulling the same changes. Unless -f/--force is specified, :hg:`phase` won't move changesets from a lower phase to a higher phase. Phases are ordered as follows:: Unless -f/--force is specified, branch will not let you set a branch name that already exists. Unless names are given, new files are ignored if they match any of the patterns in ``.hgignore``. As with add, these changes take effect at the next commit. Unlike ``merge``, rebase will do nothing if you are at the branch tip of a named branch with two heads. You will need to explicitly specify source and/or destination. Update sets the working directory's parent revision to the specified changeset (see :hg:`help parents`). Update the repository's working directory to the specified changeset. If no changeset is specified, update to the tip of the current named branch and move the active bookmark (see :hg:`help bookmarks`). Use --bypass to apply and commit patches directly to the repository, without affecting the working directory. Without --exact, patches will be applied on top of the working directory parent revision. Use --new-branch if you want to allow push to create a new named branch that is not present at the destination. This allows you to only create a new branch without forcing other changes. Use --partial to ensure a changeset will be created from the patch even if some hunks fail to apply. Hunks that fail to apply will be written to a .rej file. Conflicts can then be resolved by hand before :hg:`commit --amend` is run to update the created changeset. This flag exists to let people import patches that partially apply without losing the associated metadata (author, date, description, ...). Use --to-normal to convert largefiles back to normal files; after this, the DEST repository can be used without largefiles at all. Use -C/--clean to reset the working directory branch to that of the parent of the working directory, negating a previous branch change. Use -d/--default to disable current configuration. Use -n/--none to deactivate guards (no other arguments needed). When no guards are active, patches with positive guards are skipped and patches with negative guards are pushed. Use -s/--series to print a list of all guards in the series file (no other arguments needed). Use -v for more information. Use :hg:`diff` if you only want to see the changes made since the last qrefresh, or :hg:`export qtip` if you want to see changes made by the current patch without including changes made since the qrefresh. Use :hg:`incoming` if you want to see what would have been added by a pull at the time you issued this command. If you then decide to add those changes to the repository, you should use :hg:`pull -r X` where ``X`` is the last changeset listed by :hg:`incoming`. Use null as the changeset to remove the working directory (like :hg:`clone -U`). Use of ``sha256`` or ``sha512`` is preferred. Use the --no-backup option to discard the backup bundle once the operation completes. Use the -g/--git option to generate diffs in the git extended diff format. For more information, read :hg:`help diffs`. Use the -g/--git option to generate diffs in the git extended diff format. See :hg:`help diffs` for more information. Use the -g/--git option to keep the patch in the git extended diff format. Read the diffs help topic for more information on why this is important for preserving permission changes and copy/rename information. Use the -s/--similarity option to detect renamed files. This option takes a percentage between 0 (disabled) and 100 (files must be identical) as its parameter. With a parameter greater than 0, this compares every removed file with every added file and records those similar enough as renames. Detecting renamed files this way can be expensive. After using this option, :hg:`status -C` can be used to check which files were identified as moved or renamed. If not specified, -s/--similarity defaults to 100 and only renames of identical files are detected. Use the :hg:`qguard` command to set or print guards on patch, then use qselect to tell mq which guards to use. A patch will be pushed if it has no guards or any positive guards match the currently selected guard, but will not be pushed if any negative guards match the current guard. For example:: Use the command :hg:`update` to switch to an existing branch. Use the command :hg:`update` to switch to an existing branch. Use :hg:`commit --close-branch` to mark this branch head as closed. When all heads of a branch are closed, the branch will be considered closed. Useful to prevent inadvertent keyword expansion and to speed up execution by including only files that are actual candidates for expansion. Using the -r/--rev or -d/--date options, revert the given files or directories to their states as of a specific revision. Because revert does not change the working directory parents, this will cause these files to appear modified. This can be helpful to "back out" some or all of an earlier change. See :hg:`backout` for a related method. Valid entries for the format field are ``topic``, ``bar``, ``number``, ``unit``, ``estimate``, ``speed``, and ``item``. ``item`` defaults to the last 20 characters of the item, but this can be changed by adding either ``-`` which would take the last num characters, or ``+`` for the first num characters. Valid fields are most regular revision fields and some special fields. Valid types are: Value must be a valid OpenSSL Cipher List Format as documented at https://www.openssl.org/docs/manmaster/apps/ciphers.html#CIPHER-LIST-FORMAT. Values less than or equal to 0 always refresh. (default: 20) Verify the integrity of the current repository. When REV is not given, print a summary of the current state of the repository including the working directory. Specify -r. to get information of the working directory parent without scanning uncommitted changes. When a merge is needed, the working directory is first updated to the newly pulled changes. Local changes are then merged into the pulled changes. To switch the merge order, use --switch-parent. When cloning from servers that support it, Mercurial may fetch pre-generated data. When this is done, hooks operating on incoming changesets and changegroups may fire more than once, once for each pre-generated bundle and as well as for any additional remaining data. See :hg:`help -e clonebundles` for more. When no files are specified, "hg shelve" saves all not-clean files. If specific files or directories are named, only changes to those files are shelved. When repositories are cloned locally, their data files will be hardlinked so that they only use the space of a single repository. When running a Python that supports modern TLS versions, the default is ``tls1.1``. ``tls1.0`` can still be used to allow TLS 1.0. However, this weakens security and should only be used as a feature of last resort if a server does not support TLS 1.1+. When running on an old Python version, only ``tls1.0`` is allowed since old versions of Python only support up to TLS 1.0. When two revision arguments are given, then changes are shown between those revisions. If only one revision is specified then that revision is compared to the working directory, and, when no revisions are specified, the working directory files are compared to its first parent. When two revision arguments are given, then changes are shown between those revisions. If only one revision is specified then that revision is compared to the working directory, and, when no revisions are specified, the working directory files are compared to its parent. When utmost control over the Mercurial configuration is desired, the value of ``HGRCPATH`` can be set to an explicit file with known good configs. In rare cases, the value can be set to an empty file or the null device (often ``/dev/null``) to bypass loading of any user or system config files. Note that these approaches can have unintended consequences, as the user and system config files often define things like the username and extensions that may be required to interface with a repository. With --debug, the source (filename and line number) is printed for each config item. With --edit, start an editor on the user-level config file. With --global, edit the system-wide config file. With --local, edit the repository-level config file. With --graph the revisions are shown as an ASCII art DAG with the most recent changeset at the top. 'o' is a changeset, '@' is a working directory parent, '_' closes a branch, 'x' is obsolete, '*' is unstable, and '+' represents a fork where the changeset from the lines below is a parent of the 'o' merge on the same line. Paths in the DAG are represented with '|', '/' and so forth. ':' in place of a '|' indicates one or more revisions in a path are omitted. With -A/--all and -v/--verbose the codes used to show the status of files are:: 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 -f/--force, an existing patch of the same name will be overwritten. 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. 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 -s/--similarity, hg will attempt to discover renames and copies in the patch in the same way as :hg:`addremove`. With -v, print file permissions, symlink and executable bits. With --debug, print file revision hashes. With multiple arguments, print names and values of all config items with matching section names or section.names. With no argument, show the current branch name. With one argument, set the working directory branch name (the branch will not exist in the repository until the next commit). Standard practice recommends that primary development take place on the 'default' branch. With no argument, show the phase name of the current revision(s). With no arguments, print a list of commands with short help messages. With no arguments, print names and values of all config items. With no arguments, print the currently active guards. With arguments, set guards for the named patch. With no arguments, prints the currently active guards. With one argument, sets the active guard. With no arguments, show all open branch heads in the repository. Branch heads are changesets that have no descendants on the same branch. They are where development generally takes place and are the usual targets for update and merge operations. With no revision specified, revert the specified files or directories to the contents they had in the parent of the working directory. This restores the contents of files to an unmodified state and unschedules adds, removes, copies, and renames. If the working directory has two parents, you must explicitly specify a revision. With one argument of the form section.name, print just the value of that config item. With one argument, renames the current patch to PATCH1. With two arguments, renames PATCH1 to PATCH2. With one of -p/--public, -d/--draft or -s/--secret, change the phase value of the specified revisions. With the --remote option, this will check the default paths for incoming and outgoing changes. This can be time-consuming. With the --switch-parent option, the diff will be against the second parent. It can be useful to review a merge. With the -d/--diffstat option, if the diffstat program is installed, the result of running diffstat on the patch is inserted. 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. Without argument, pops off the top of the patch stack. If given a patch name, keeps popping off patches until the named patch is at the top of the stack. Without the -a/--text option, annotate will avoid processing files it detects as binary. With -a, annotate will annotate the file anyway, although the results will probably be neither useful nor desirable. Without the -a/--text option, diff will avoid generating diffs of files it detects as binary. With -a, diff will generate a diff anyway, probably with undesirable results. Without the -a/--text option, export will avoid generating diffs of files it detects as binary. With -a, export will generate a diff anyway, probably with undesirable results. You can change bundle format with the -t/--type option. See :hg:`help bundlespec` for documentation on this format. By default, the most appropriate format is used and compression defaults to bzip2. You can import a patch straight from a mail message. Even patches as attachments work (to use the body part, it must have type text/plain or text/x-patch). From and Subject headers of email message are used as default committer and commit message. All text/plain body parts before first diff are added to the commit message. You can optionally mark selected transplanted changesets as merge changesets. You will not be prompted to transplant any ancestors of a merged transplant, and you can merge descendants of them normally instead of transplanting them. You can register an existing patch inside the patch directory with the -e/--existing flag. You can rewrite the changelog message with the --filter option. Its argument will be invoked with the current changelog message as $1 and the patch as $2. You can use OpenSSL's CA certificate file if your platform has one. On most Linux systems this will be ``/etc/ssl/certs/ca-certificates.crt``. Otherwise you will have to generate this file manually. The form must be as follows:: [bar] eggs=ham green= eggs [bugzilla] bzurl=http://my-project.org/bugzilla user=bugmail@my-project.org password=plugh version=xmlrpc template=Changeset {node|short} in {root|basename}. {hgweb}/{webroot}/rev/{node|short}\n {desc}\n strip=5 [bugzilla] bzurl=http://my-project.org/bugzilla user=bugmail@my-project.org password=plugh version=xmlrpc+email bzemail=bugzilla@my-project.org template=Changeset {node|short} in {root|basename}. {hgweb}/{webroot}/rev/{node|short}\n {desc}\n strip=5 [bugzilla] host=localhost password=XYZZY version=3.0 bzuser=unknown@domain.com bzdir=/opt/bugzilla-3.2 template=Changeset {node|short} in {root|basename}. {hgweb}/{webroot}/rev/{node|short}\n {desc}\n strip=5 [committemplate] changeset = {desc}\n\n HG: Enter commit message. Lines beginning with 'HG:' are removed. HG: {extramsg} HG: -- HG: user: {author}\n{ifeq(p2rev, "-1", "", "HG: branch merge\n") }HG: branch '{branch}'\n{if(activebookmark, "HG: bookmark '{activebookmark}'\n") }{subrepos % "HG: subrepo {subrepo}\n" }{file_adds % "HG: added {file}\n" }{file_mods % "HG: changed {file}\n" }{file_dels % "HG: removed {file}\n" }{if(files, "", "HG: no files changed\n")} [committemplate] changeset = {desc}\n\n HG: Enter commit message. Lines beginning with 'HG:' are removed. HG: {extramsg} HG: ------------------------ >8 ------------------------ HG: Do not touch the line above. HG: Everything below will be removed. {diff()} [committemplate] listupfiles = {file_adds % "HG: added {file}\n" }{file_mods % "HG: changed {file}\n" }{file_dels % "HG: removed {file}\n" }{if(files, "", "HG: no files changed\n")} [extensions] bugzilla = [foo] eggs=large ham=serrano eggs=small [foo] ham=prosciutto eggs=medium bread=toasted [graph] # 2px width default.width = 2 # red color default.color = FF0000 [hooks] # run bugzilla hook on every change pulled or pushed in here incoming.bugzilla = python:hgext.bugzilla.hook [hostfingerprints] hg.intevation.de = fc:e2:8d:d9:51:cd:cb:c1:4d:18:6b:b7:44:8d:49:72:57:e6:cd:33 hg.intevation.org = fc:e2:8d:d9:51:cd:cb:c1:4d:18:6b:b7:44:8d:49:72:57:e6:cd:33 [hostsecurity] minimumprotocol = tls1.2 hg.example.com:minimumprotocol = tls1.1 [keyword] # expand keywords in every python file except those matching "x*" **.py = x* = ignore [keywordset] # prefer svn- over cvs-like default keywordmaps svn = True [paths] my_server = https://example.com/my_path my_server:pushurl = ssh://example.com/my_path [paths] my_server = https://example.com/my_repo local_path = /home/me/repo [revsetalias] issue(a1) = grep(r'\bissue[ :]?' ## a1 ## r'\b|\bbug\(' ## a1 ## r'\)') [spam] eggs=ham green= eggs [spam] eggs=large ham=serrano eggs=small [usermap] user@emaildomain.com=user.name@bugzilladomain.com [web] baseurl=http://my-project.org/hg [websub] issues = s|issue(\d+)|issue\1|i italic = s/\b_(\S+)_\b/\1<\/i>/ bold = s/\*\b(\S+)\b\*/\1<\/b>/ ``--full`` will make sure the converted changesets contain exactly the right files with the right content. It will make a full conversion of all files, not just the ones that have changed. Files that already are correct will not be changed. This can be used to apply filemap changes when converting incrementally. This is currently only supported for Mercurial and Subversion. ``--tool`` can be used to specify the merge tool used for file merges. It overrides the HGMERGE environment variable and your configuration files. See :hg:`help merge-tools` for options. ``abort`` The command is aborted. ``false`` Alias for ``ignore``. ``hotpath`` Show a tree-based display containing the hot path of execution (where most time was spent). ``bymethod`` Show a table of methods ordered by how frequently they are active. ``byline`` Show a table of lines in files ordered by how frequently they are active. ``json`` Render profiling data as JSON. ``ignore`` Don't print a warning. ``ls`` Use Python's built-in instrumenting profiler. This profiler works on all platforms, but each line number it reports is the first line of a function. This restriction makes it difficult to identify the expensive parts of a non-trivial function. ``stat`` Use a statistical profiler, statprof. This profiler is most useful for profiling commands that run for longer than about 0.1 seconds. ``metadata`` is the default field which is used when no fields are specified. You can match more than one field at a time. ``text`` Generate a profiling report. When saving to a file, it should be noted that only the report is saved, and the profiling data is not kept. ``kcachegrind`` Format profiling data for kcachegrind use: when saving to a file, the generated file can directly be loaded into kcachegrind. ``true`` Alias for ``warn``. ``warn`` Print a warning message on POSIX platforms, if a file with a non-portable filename is added (e.g. a file with a name that can't be created on Windows because it contains reserved parts like ``AUX``, reserved characters like ``:``, or would cause a case collision with an existing file). aliases: %s bar.prefix = secure.example.org bar.key = path/to/file.key bar.cert = path/to/file.cert bar.schemes = https committer = Bugzilla user expr % "{template}" foo.prefix = hg.intevation.de/mercurial foo.username = foo foo.password = bar foo.schemes = http https hg add/remove/copy/rename work as usual, though you might want to use git-style patches (-g/--git or [diff] git=1) to track copies and renames. See the diffs help topic for more information on the git diff format. hg diff -r 1.3::1.5 hg files "set:**.c and not encoding('UTF-8')" hg files "set:grep(magic) and not binary()" hg forget "set:hgignore() and not ignored()" hg log -r "(keyword(bug) or keyword(issue)) and not ancestors(tag())" hg log -r "1.3::1.5 and keyword(bug) and file('hgext/*')" hg log -r "branch(default) and 1.5:: and not merge()" hg log -r "branch(default)" hg log -r "head() and not closed()" hg log -r "sort(date('May 2008'), user)" hg revert "set:copied() and binary() and size('>1M')" hg revert "set:revs('wdir()', added())" hg status -A "set:binary()" hg update :@ http://server/(.*)-hg/ = http://hg.server/\1/ kwexpand refuses to run if given files contain local changes. kwshrink refuses to run if given files contain local changes. latest = log --limit 5 patternname = s/SEARCH_REGEX/REPLACE_EXPRESSION/[i] qnew creates a new patch on top of the currently-applied patch (if any). The patch will be initialized with any outstanding changes in the working directory. You may also use -I/--include, -X/--exclude, and/or a list of files after the patch name to add only changes to matching files to the new patch, leaving the rest as uncommitted modifications. qselect can change the guards on applied patches. It does not pop guarded patches by default. Use --pop to pop back to the last applied patch that is not guarded. Use --reapply (which implies --pop) to push back to the current patch afterwards, but skip guarded patches. ssh://example.com//tmp/repository stable5 = latest -b stable $ hg log --template "{bookmarks % '{bookmark}{ifeq(bookmark, active, '*')} '}\n" $ hg log --template "{ifcontains(rev, revset('.'), '@')}\n" $ hg log --template "{revset('parents(%d)', rev) % '{desc|firstline}\n'}" $ hg log --template "{splitlines(desc) % '**** {line}\n'}" $ hg log --template "{startswith('template', firstline(desc))}\n" $ hg log --template "{word(0, desc)}\n" $ hg log -r . --template "{latesttag('re:^.*-rc$') % '{tag}, {changes}, {distance}'}\n" $ hg log -r 0 --template "files: {join(files, ', ')}\n" $ hg log -r 0 --template "files:\n{files % ' {file}\n'}" $ hg log -r 0 --template "pythonfiles: {join(files('**.py'), ', ')}\n" $ hg log -r 0 --template "{date(date, '%Y')}\n" $ hg log -r 0 --template "{fill(desc, 30)}" $ hg log -r 0 --template "{ifeq(branch, 'default', 'on the main branch', 'on branch {branch}')}\n" $ hg log -r 0 --template "{join(extras, '\n')}\n" $ hg log -r 0 --template "{label('changeset.{phase}', node|short)}\n" $ hg log -r 0 --template "{localdate(date, 'UTC')|date}\n" $ hg log -r 0 --template "{separate(' ', node, bookmarks, tags}\n" $ hg log -r 0 --template "{sub(r'^.*\n?\n?', '', desc)}\n" $ hg tip --template "{date|isodate}\n" 2008-08-21 18:22 +0000 $ hg tip --template "{if(author, '{author}\n')}" :hg:`clone` will automatically define this path to the location the repository was cloned from. @ 6[tip] 038383181893 2009-04-27 18:04 -0500 stefan | Add theta | o 5 140988835471 2009-04-27 18:04 -0500 stefan | Add eta | o 4 122930637314 2009-04-27 18:04 -0500 stefan | Add zeta | o 3 836302820282 2009-04-27 18:04 -0500 stefan | Add epsilon | o 2 989b4d060121 2009-04-27 18:04 -0500 durin42 | Add beta and delta. | o 1 081603921c3f 2009-04-27 18:04 -0500 durin42 | Add gamma | o 0 d8d2fcd0e319 2009-04-27 18:04 -0500 durin42 Add alpha Changesets in secret phase are not exchanged with the server. This applies to their content: file names, file contents, and changeset metadata. For technical reasons, the identifier (e.g. d825e4025e39) of the secret changeset may be communicated to the server. Configuring the ``share`` extension can lead to significant resource utilization reduction, particularly around disk space and the network. This is especially true for continuous integration (CI) environments. Environment variables with empty values may not be passed to hooks on platforms such as Windows. As an example, ``$HG_PARENT2`` will have an empty value under Unix-like platforms for non-merge changesets, while it will not be available at all under Windows. For example, a value of ``.`` will push the working directory's revision by default. For example, if a multibyte character ending with backslash (0x5c) is followed by the ASCII character 'n' in the customized template, the sequence of backslash and 'n' is treated as line-feed unexpectedly (and the multibyte character is broken, too). For some problematic encodings (see :hg:`help win32mbcs` for detail), this customization should be configured carefully, to avoid showing broken characters. Git and Subversion subrepos are also supported:: If parsing raw command output is too complicated, consider using templates to make your life easier. If you need to invoke several ``hg`` processes in short order and/or performance is important to you, use of a server-based interface is highly recommended. It is possible to create aliases with the same names as existing commands, which will then override the original definitions. This is almost always a bad idea! Note that ``.hgsub`` does not exist by default in Mercurial repositories, you have to create and add it to the parent repository before using subrepositories. Revsets specifying bookmarks will not result in the bookmark being pushed. See :hg:`help -e share` for more. See :hg:`help revsets` for more. Some global configuration options such as ``-R`` are processed before shell aliases and will thus not be passed to aliases. The ``json`` and ``xml`` styles are considered experimental. While they may be attractive to use for easily obtaining machine-readable output, their behavior may change in subsequent versions. The more specific you are in your filename patterns the less you lose speed in huge repositories. The registry key ``HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mercurial`` is used when running 32-bit Python on 64-bit Windows. The rules will first apply when files are touched in the working directory, e.g. by updating to null and back to tip to touch all files. These styles may also exhibit unexpected results when dealing with certain encodings. Mercurial treats things like filenames as a series of bytes and normalizing certain byte sequences to JSON or XML with certain encoding settings can lead to surprises. When :hg:`push` is executed without a ``-r`` argument, the revset defined by this sub-option is evaluated to determine what to push. echo = !echo $@ purge = !$HG status --no-status --unknown -0 re: | xargs -0 rm -f where ``path/to/nested`` is the checkout location relatively to the parent Mercurial root, and ``https://example.com/nested/repo/path`` is the source repository path. The source can also reference a filesystem path. # 'none' turns off all effects status.clean = none status.copied = none # 1) only 'gollum' can commit to branch 'ring'; # 'gollum' and anyone else can still commit to any other branch. ring = !gollum # 2) only members of the group 'hobbit' can commit to branch 'lake'; # 'hobbit' members and anyone else can still commit to any other branch. lake = !@hobbit # A bad user is denied on all branches: * = bad-user # A few users are allowed on branch-a: branch-a = user-1, user-2, user-3 # Blank so it inherits the style of the surrounding label changeset.public = changeset.draft = changeset.secret = # Changing the priority of preconfigured tool meld.priority = 0 # Define new tool myHtmlTool.args = -m $local $other $base $output myHtmlTool.regkey = Software\FooSoftware\HtmlMerge myHtmlTool.priority = 1 # Disable a preconfigured tool vimdiff.disabled = yes # Everyone (except for "user6" and "@hg-denied" - see acl.deny above) # will have write access to any file under the "resources" folder # (except for 1 file. See acl.deny): src/main/resources/** = * # Everyone is allowed on branch-for-tests: branch-for-tests = * # Everyone is denied to the frozen branch: frozen-branch = * # Group "hg-denied" will not have write access to any file: ** = @hg-denied # Nobody will be able to change "DONT-TOUCH-THIS.txt", despite # everyone being able to change all other files. See below. src/main/resources/DONT-TOUCH-THIS.txt = * # Only one user is allowed on branch-b: branch-b = user-1 # The super user is allowed on any branch: * = super-user # To match everyone, use an asterisk for the user: # my/glob/pattern = * # Use this if you want to check access restrictions at commit time pretxncommit.acl = python:hgext.acl.hook # Use this if you want to check access restrictions for pull, push, # bundle and serve. pretxnchangegroup.acl = python:hgext.acl.hook # User "doc_writer" has write access to any file under the "docs" # folder: docs/** = doc_writer # User "jack" and group "designers" have write access to any file # under the "images" folder: images/** = jack, @designers # You can also deny access based on file paths: # add new command called meld, runs meld (no need to name twice). If # the meld executable is not available, the meld tool in [merge-tools] # will be used, if available meld = # add new command called vimdiff, runs gvimdiff with DirDiff plugin # (see http://www.vim.org/scripts/script.php?script_id=102) Non # English user, be sure to put "let g:DirDiffDynamicDiffText = 1" in # your .vimrc vimdiff = gvim -f "+next" \ "+execute 'DirDiff' fnameescape(argv(0)) fnameescape(argv(1))" # one email for all outgoing changesets outgoing.notify = python:hgext.notify.hook # switch to regexp syntax. syntax: regexp ^\.pc/ # use glob syntax. syntax: glob # user6 will not have write access to any file: ** = user6 $ cd test $ hg serve $ dd if=/dev/urandom of=randomdata count=2000 $ hg add --large randomdata $ hg commit -m "add randomdata as a largefile" $ hg add --lfsize 2 $ hg lfconvert --size 10 oldrepo newrepo $ hg log -r . -Tnodedate $ hg paths zc-test = http://example.com:8000/test $parent1, $plabel1 - filename, descriptive label of first parent $child, $clabel - filename, descriptive label of child revision $parent2, $plabel2 - filename, descriptive label of second parent $root - repository root $parent is an alias for $parent1. %include ~/.hgrc.d/$HOST.rc %s in %s should not have %s line endings (default: the tool name) *.elc *.pyc *~ + for addition - for subtraction * for multiplication / for floor division (division rounded to integer nearest -infinity) - ``$HOME/.hgrc`` (on Unix, Plan9) - ``%USERPROFILE%\mercurial.ini`` (on Windows) - ``/.hg/hgrc`` (per-repository) - ``$HOME/.hgrc`` (per-user) - ``${XDG_CONFIG_HOME:-$HOME/.config}/hg/hgrc`` (per-user) - ``/etc/mercurial/hgrc`` (per-installation) - ``/etc/mercurial/hgrc.d/*.rc`` (per-installation) - ``/etc/mercurial/hgrc`` (per-system) - ``/etc/mercurial/hgrc.d/*.rc`` (per-system) - ``/default.d/*.rc`` (defaults) - ``/.hg/hgrc`` (per-repository) - ``$home/lib/hgrc`` (per-user) - ``/lib/mercurial/hgrc`` (per-installation) - ``/lib/mercurial/hgrc.d/*.rc`` (per-installation) - ``/lib/mercurial/hgrc`` (per-system) - ``/lib/mercurial/hgrc.d/*.rc`` (per-system) - ``/default.d/*.rc`` (defaults) - ``/.hg/hgrc`` (per-repository) - ``%USERPROFILE%\.hgrc`` (per-user) - ``%USERPROFILE%\Mercurial.ini`` (per-user) - ``%HOME%\.hgrc`` (per-user) - ``%HOME%\Mercurial.ini`` (per-user) - ``HKEY_LOCAL_MACHINE\SOFTWARE\Mercurial`` (per-installation) - ``\hgrc.d\*.rc`` (per-installation) - ``\Mercurial.ini`` (per-installation) - ``/default.d/*.rc`` (defaults) - web - paths - collections -f -> ::. -d x -> date(x) -k x -> keyword(x) -m -> merge() -u x -> user(x) -b x -> branch(x) -P x -> !::x -l x -> limit(expr, x) .. webcommandsmarker .hgtags = release_engineer :``restapi``: Bugzilla REST-API, Bugzilla 5.0 and later. :``xmlrpc``: Bugzilla XMLRPC interface. :``xmlrpc+email``: Bugzilla XMLRPC and email interfaces. :``3.0``: MySQL access, Bugzilla 3.0 and later. :``2.18``: MySQL access, Bugzilla 2.18 and up to but not including 3.0. :``2.16``: MySQL access, Bugzilla 2.16 and up to but not including 2.18. :``serve``: changesets received via http or ssh :``pull``: changesets received via ``hg pull`` :``unbundle``: changesets received via ``hg unbundle`` :``push``: changesets sent or received via ``hg push`` :``bundle``: changesets sent via ``hg unbundle`` :``{bug}``: The Bugzilla bug ID. :``{root}``: The full pathname of the Mercurial repository. :``{webroot}``: Stripped pathname of the Mercurial repository. :``{hgweb}``: Base URL for browsing Mercurial repositories. = All other prefix, infix and postfix operators have lower priority than ``##``. For example, ``a1 ## a2~2`` is equivalent to ``(a1 ## a2)~2``. Alternatively specify "ssh -C" as your ssh command in your configuration file or with the --ssh command line option. An alternative syntax is ``x..y``. Default ``changeset {node|short} in repo {root} refers to bug {bug}.\ndetails:\n\t{desc|tabindent}`` Default: serve. Deprecation: The win32text extension requires each user to configure the extension again and again for each clone since the configuration is not copied when cloning. For example, if installed in ``/shared/tools/bin/hg``, Mercurial will look in ``/shared/tools/etc/mercurial/hgrc``. Options in these files apply to all Mercurial commands executed by any user in any directory. For example:: On Plan 9 and Unix, most of this file will be ignored if it doesn't belong to a trusted user or to a trusted group. See :hg:`help config.trusted` for more details. On Plan9, the following files are consulted: On Unix, the following files are consulted: On Windows 9x, ``%HOME%`` is replaced by ``%APPDATA%``. On Windows, the following files are consulted: Patterns specified in ``.hgignore`` are not rooted. Please see :hg:`help hgignore` for details. Patterns specified in other than ``.hgignore`` are always rooted. Please see :hg:`help patterns` for details. Pulling a draft changeset from a publishing server does not mark it as public on the server side due to the read-only nature of pull. SNI not supported by Python install; may have connectivity issues with some servers See also the ``[usermap]`` section. Servers running older versions of Mercurial are treated as publishing. TLS 1.2 not supported by Python install; network connections lack modern security We have therefore made the ``eol`` as an alternative. The ``eol`` uses a version controlled file for its configuration and each clone will therefore use the right settings from the start. [acl.allow.branches] [acl.allow.branches] # Empty [acl.allow] # Empty [acl.allow] # if acl.allow is not present, all users are allowed by default # empty acl.allow = no users allowed [acl.deny.branches] [acl.deny] # 3) only 'gollum' can change the file below; # 'gollum' and anyone else can still change any other file. /misty/mountains/cave/ring = !gollum [acl.deny] # This list is checked first. If a match is found, acl.allow is not # checked. All users are granted access if acl.deny is not present. # Format for both lists: glob pattern = user, ..., @group, ... [acl] # Allow or deny access for incoming changes only if their source is # listed here, let them pass otherwise. Source is "serve" for all # remote access (http or ssh), "push", "pull" or "bundle" when the # related commands are run locally. # Default: serve sources = serve [blackbox] # limit the size of a log file maxsize = 1.5 MB # rotate up to N log files when the current one gets too big maxfiles = 3 [blackbox] track = * # dirty is *EXPENSIVE* (slow); # each log entry indicates `+` if the repository is dirty, like :hg:`id`. dirty = True # record the source of log messages logsource = True [blackbox] track = command, commandfinish, commandexception, exthook, pythonhook [blackbox] track = incoming [color] status.modified = blue bold underline red_background status.added = green bold status.removed = red bold blue_background status.deleted = cyan bold underline status.unknown = magenta bold underline status.ignored = black bold [color] terminfo.dim = \E[2m [decode] # recompress gzip files when writing them to the working dir (we # can safely omit "pipe:", because it's the default) *.gz = gzip [decode] ** = cleverdecode: # or ** = macdecode: [defaults] log = -v status = -m [diff-tools] kdiff3.diffargs=--L1 '$plabel1' --L2 '$clabel' $parent $child [email] cc = [email] from = Joseph User method = /usr/sbin/sendmail # charsets for western Europeans # us-ascii, utf-8 omitted, as they are tried first and last charsets = iso-8859-1, iso-8859-15, windows-1252 [email] from = My Name to = recipient1, recipient2, ... cc = cc1, cc2, ... bcc = bcc1, bcc2, ... reply-to = address1, address2, ... [encode] # uncompress gzip files on checkin to improve delta compression # note: not necessarily a good idea, just an example *.gz = pipe: gunzip [extdiff] # add new command that runs GNU diff(1) in 'context diff' mode cdiff = gdiff -Nprc5 ## or the old way: #cmd.cdiff = gdiff #opts.cdiff = -Nprc5 [extdiff] kdiff3 = [extensions] # (the churn extension will get loaded from Mercurial's path) churn = # (this extension will get loaded from the file specified) myfeature = ~/.hgext/myfeature.py [extensions] # disabling extension bar residing in /path/to/extension/bar.py bar = !/path/to/extension/bar.py # ditto, but no path was supplied for extension baz baz = ! [extensions] foo = [extensions] myfeature = ~/.hgext/myfeature.py [extensions] win32text = [encode] ** = cleverencode: # or ** = macencode: [factotum] executable = /bin/auth/factotum mountpoint = /mnt/factotum service = hg [hgk] path = /location/of/hgk [hgk] vdiff=vdiff [histedit] defaultrev = only(.) & draft() [histedit] dropmissing = True [histedit] linelen = 120 # truncate rule lines at 120 characters [histedit] singletransaction = True [hooks] [hooks] # one email for each incoming changeset incoming.notify = python:hgext.notify.hook # one email for all incoming changesets changegroup.notify = python:hgext.notify.hook [hooks] # update working directory after adding changesets changegroup.update = hg update # do not use the site-wide hook incoming = incoming.email = /my/email/hook incoming.autobuild = /my/build/hook # force autobuild hook to run before other incoming hooks priority.incoming.autobuild = 1 [hooks] pretxnchangegroup.crlf = python:hgext.win32text.forbidcrlf # or pretxnchangegroup.cr = python:hgext.win32text.forbidcr [hooks] pretxncommit.crlf = python:hgext.win32text.forbidcrlf # or pretxncommit.cr = python:hgext.win32text.forbidcr [largefiles] minsize = 2 [largefiles] patterns = *.jpg re:.*\.(png|bmp)$ library.zip content/audio/* [log.changeset changeset.secret|changeset: 22611:6f0a53c8f587] [merge-patterns] **.c = kdiff3 **.jpg = myimgmerge [merge-tools] # Override stock tool location kdiff3.executable = ~/bin/kdiff3 # Specify command line kdiff3.args = $base $local $other -o $output # Give higher priority kdiff3.priority = 1 [mq] git = auto/keep/yes/no [mq] keepchanges = True [mq] secret = True [notify] config = /path/to/subscriptionsfile [pager] attend-cat = false [pager] ignore = version, help, update [pager] pager = less -FRX [patchbomb] flagtemplate = "{separate(' ', ifeq(branch, 'default', '', branch|upper), flags)}" [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 [paths] /projects/a = /srv/tmprepos/a /projects/b = c:/repos/b / = /srv/repos/* /user/bob = /home/bob/repos/** [paths] alias1 = URL1 alias2 = URL2 ... [patterns] **.py = native **.vcproj = CRLF **.txt = native Makefile = LF **.jpg = BIN [phases] new-commit = secret [phases] publish = False [repository] native = LF [reposubs] # key is repo pattern, value is a comma-separated list of subscriber emails pattern = user@host [reposubs] */widgets#branch(release) = qa-team@example.com [revsetalias] h = heads() d(s) = sort(s, date) rs(s, k) = reverse(sort(s, k)) [schemes] gcode = http://{1}.googlecode.com/hg/ [schemes] py = http://code.python.org/hg/ [schemes] py = http://hg.python.org/ bb = https://bitbucket.org/ bb+ssh = ssh://hg@bitbucket.org/ gcode = https://{1}.googlecode.com/hg/ kiln = https://{1}.kilnhg.com/Repo/ [templatealias] r = rev rn = "{r}:{node|short}" leftpad(s, w) = pad(s, w, ' ', True) [templates] nodedate = "{node|short}: {date(date, "%Y-%m-%d")}\n" [ui] username = Firstname Lastname verbose = True [usersubs] # key is subscriber email, value is a comma-separated list of repo patterns user@host = pattern [web] pygments_style =