P'#1!1!1#1#!24E23z2-2-2 3@3T`333838*4Dc484<4>50]5(5>5H5?6\6w6;6$6/6F7Bd7F7/7.8M8f8{88A8T8595939,:G:Z:u:::*::;!;0;A; Z; h;";;';*; <<47<l<q<@OZA|B'DDyEEERFF:G5GtHjvH2H2IGIUI/JK++K-WKKKSK:L4IL~LL8$ME]MMM"MNN5=N0sN9N@N,O:LO+O,O)O- P'8P+`PPPQ2hQ4Q)Q!Q$R)AR!kRRR.R$R/S?S#USyS=SS1SAT.[T9TJT)UG9U2UU-U0U-V+KV!wV V1VVWW33W,gWW.W%W$X#*XFNX'X+XXX3Y0EY-vY?YY)Z*ZZZ[5[9M[f[[yq\^\YJ]]PE^8^^W_h_^``9bbrc]dyeeHepffg:g)#h,MiziFjdjGklmfm,n(o:ogZop/Iqyq qXqqr]sOtLFuuf^v/v0v&w7wwxzy'+z'Sz{z!z!zjz4H{\}{{k|3}}`~-/`O]N>A"τ'^8ywZ*M3ӆ:XB.<ʇ7L?e7:*De?5@ Ja=r(]%G,J!4lL*L.f6A̍7:F;Ec:g42׏: )E&o?E֐CH`1Fۑ6"#Y/}%͒4&(Ovޓ7U63Ĕ./'\W*:ߕD\_nD+Op@IA̘'U0}4MN1X?ٚL6fBZg;T' 0La|-nǡ{6C$""E 7"x2hDQh5ON=Rb o=XYQ=B $2W0ܹ2 %@1f-Aƺ:C!ͽH38l3..!**E/p](['+=6(# Ab!~:#^}6o-D*SD,PmPo >yY] "6(1=0o3ragmgRIbKEJ)5HN~3%I'mqHs:`p8d< Zf^$RmwsY2\MlZo  +ySdiiH/x[[ Su  m c x j ^d ^ _"  'q!qh,f5/*(K)l7I;ofb=|~:q\ S!4""h#F$O%T&.&( U(v()*I,L-:.$/,001*b23l4@4.6B6[(7{788Q99Y:A;>_;H=l=(T>}>'?|(??@ynAAB CHE?OEYEvF`GFG,H%I!IXI8J KK L M<MNb-NuNcOXjO'O O5O(.P2WP1P$P%P&QF.Q6uQ(Q'Q3Q!1R4SRRR8SST<UUY_VVUWTMX_X!YB$YgY4mZiZW [d[M[[_\5\t/^+^^_[U``]abVc?d[d-el fyfDgrg\hh{ihjqjfkjkllmk nZwnnRopp7rm's^sstDQuLuu|v@wwxbYyey"z {{j|C}a~<b~k~Z mfe: MFsF O\] g3|5F4{5 bۑ>’EcLdus y͛a`tw jz{hjFOkqtvbqoԨzDq>45(+ܮQZwf>[Y3\)@ ն:/,ܺKMG,hpWzto[9('b+E?EO(bxTPY-VU'4P\5c"+NXjC>P7a8%k^9O}/?Voj&~EJHHXH&//B4r7'9#A@eJ!>>R3CC EM=;5 BC/YW@h?D, 96p-LEfZW0BJCH6fQ7iTZFZRQA)K\7:-rpE"W6z-RY2,oXvpH'57OTpWak?3 AA'.%$/% UDvC$ePy/6sOfeezn\^Dp+Bwn{ % # p*  ULL2c2wv+ *7bf@.0*.2ayM@o kco`)&!h o !"#4$$"%%}&w)'|'+(WJ((\) )8*$,s,Z0-(-0-(-7.8F.4.*.~.^//133*.4Y4r5j066i677^8'::Bc;:<<L=h=g?^@aA<bBBSCCD>SEEF?6H9vH~H>/I#nII:"J]JKRLLU~MM.zNOe0PePPQ-RSTCUVv WWGXvX4LYY* Z6ZD.\s\\]?^(^`|`Q1a-a$a:aAbSb^coccdWeXFfyfgh`it jDjZj^!kl m3mxm<tnoEppq$rcr;7sss tteufu\vwpw)xyyuz{|`b}]}0!~R~~o69py-*X1w]}N=6Atk-NJ3HDߏ3$X,Hb<| 1>)#5!\W3WSܢ 0P; }mo`[hy9rEȫAIPBmݬhK_]mxnUxرQײ8cA\ZDb=G-<6j- ϼ3ٽ  r:7>6?.v%2605\fC[r;SiVl].!8PC.D+I>u)b+Am)#L&D^*IH{,83SqvL:2m0!1/90i0I=39q',9 9Z+1?#FcF 7uW"#,P%j$E4SO>L=/Dm+Z:9<tI2..h]4H=DE=C3Je~; U%6 Z"}3*j^KodP %]#,g^ pz &D8}MqE8L"yoC-9C@OQ=M=Lof y 1 - G *. ,Y V 7 # >9 x ~ *&%Qw6*)DY$02Q!Eg $Ax$ h0W1A.-9H0 c q/!!V+"%"J"$"T$Pm$%R'( +(L(vd((()!m*+,T,A-a- Y.z.6 /%D/Nj///0M11222{3042G4Sz4Z4)55!5 6- 6!N6Ip6'6 66478zb9#9:_:B~:[:8;V;!<A<]<0t<<*<<==xs>/>a? ~???p?>J@U@3@-AAA\AWBEB*C>CSCXmCpC7DDEF0G: HoHII,PJ}JmJ KK%K6K?EKdKK1LO1OhQOOPQRJRh[SLSeTDwT5T?TJ2U}UU/UUUxV W5 Y.@Y(oYY%YYY ZZ 0Z;Z DZNZ]ZqZZZ ZZZZ ZZ [[5([ ^[l[W\Sv\*\M\-C]q]C ^:Q^D^^,_`aVafqaaaaz bbbJbUbULczc1dOd~dinee[f%uff#f"f,f'g*@g%kgg0g,gii Wj5xj;j6j5!kWk_kgk okzkkkkkkkkkkkkkkkkkkll ll0l BlLl Ul vl!llll l ll!lIm,im mmm!m(m n!6n"Xn{n n7n nn1n #o .o ;o FoQo qo {o o o oooooooo p&'pNpnpp(ppp0p.q1q.:q%iqqq1q0q"r:r*Rr}rrrrrr- s:s?Zs3s*ss" t)0t$Zt+t&t%t-tB&u(iu+u.u uuvF v gvrv(v'v(v)v'%w&Mw+tw%ww.w!x &x&Gxnx+x%xx x*y@ySy eyoyy y,y:y&zFzezzz#zzzzzz3{F{d{|{{{{#{|$#|H|6d|| | ||} }I6}*}'}!}} ~!~'@~h~{~"~#~'~0%8^q2&*-."\++D׀,I+g);$=[,w,тo]xӃ+I"f,҄+).UX+ȅ:/ 5 @HM&^'>Ȉ%J-xb|`??ڌ((ClA?ݍ+<1hG5%9>)xs#:"RPuƐݐ7>AWE7A3'u5Ӓ3(&'O4wEQ-D(r':Ô  RPlՕbB7:Br)ߗƘؘ ="5>G*a ? ϛ.ٛ&&/VYdC!Rʝ4MRE$ ;#Y_+)S>cCϠ8١&59%o)},=j49A'19Y)$ӥu<nJ&40Ъhҳ.ڴ 7ͶXk^ʷUeue۸wAz*43_ >&40O3;&9$Qv $Eۼ&!H'g###׽1%-)S+} %þ- /,P}4AͿ 3J\p83l1#&$ATD0u\nLpry acd"X{U) a@t-\8808Q pE:`7.gfC5oo<zC?WT[q;U n_=> fKU0~9775(^N;aLIh oX,{eg?d%R8nO'<a1`--B<pOW=UXD1wT0n7a)92Ql xT@p>Yy)u.BHk.3OD7\jr`|E#= 6 FS u ? 7P T A 1 gQ T E[T[D ]Q4  @0H<y6Xs%c~isG%,"ZOrItg o]!|#N$^i$ $0$B%F]%%g% 'D&(Hk(9(d(S))Q**+x,;-nZ.Z/$00411 22<3443M4G4;45+%5Q5Z5a5"55l6068_8# :!D:f:J;ej;D;h=F~>7? ?h@p@'@?@@@AyAATBMC6kC#DDrEF F!F2F;FBF HHPH:II]J KK+L+L+MFM.M'M1$NVN!iN+N(N%NOO#"OFO2P Q*Q,%R8RR RR.RR>R^,SBS/SSvTT U1U!UUVYWFX/Y5Y.ZLJZZP\U\ Y\)f\\1\Q\7-]ce^e^/_G_ `a0b$cBcC dhdd<e fAfSfHg$Wh|h5iniVk`uk5l mm>,mkm+mmmmnqo+ooooo# p 0p:p;Lp ppp3qGq$Arfr yrrtt:t t uuFu`usuu u uuuuu\v%wy~yz=6{8t||}}}}~%> Y f2ZZiă :E,r)4,҆E((1Z . !1/Fa7OF0w5GBőYb("ɔ(B-pJ0{ByEz"}BZ/i,9ݛ $;`m}vۡ]wբk'v MO<bB mƪ4ϫi IyUϮD g/ @ȴj tWܶn^Iwƻ=P^kGʽu0#%ݾLP&Fa s|=:>C SQ-$+ PokL=*U/Gmw;#4 'PK 1T`Le>}o<F{7n5AAw=}>_ {+p $-.\ @a% n!$:AYpnT=4urN^=Rjr!+ 4B4\Q!1I%*27> #}-i591o3[s%pSbs(CY98*v+1  )      >. m q  y    C ] E+]= {slj/W} %@I]Onpmp +~BKK9,*&=`[ +g:1rG74l[w u r!5"L""*####$$=%%k&9'''1(-9(+g(;(7()))&*+-+ ,,=A-=---;w.,.. .!/"/+/$0/$U/z//00.0/1= 2^2v4}46L678Hz99Zu:_:0<"3=V>O?l? AB4CCBDExF_xGH1I6II[JLLj|MM'NNOE|PP#QR=SSTUhV\WWXX?YQY7Y2 Z5[/|['[([)[T'\8|\U\ ]~']]wM^^)z__G`2b`0c.ccdCevVeff94gngzi+i(ijklRmW.oTo/o# p"/peRpmp(&q OqZr_sKsGttuivQwax}qyyoze{wn{~{Se|!||N|H}}r~_qm:5Q4-(u1:݉&I A4?tt:] \ovx=Q-=cjΔQ17inrT$7yu'MB2Ù*T.krDir!HCGNաlNb 3ͣң#/nBa2!EWXɧ+CS$M)wWE`F"!׭<nRyAY #/>ӸP&.w/Sּ*Ts#zfjXG\R2E_x~e{|o/4Q&).!Km 82Aa}  <& /=3O&# 94 CM_f) 6)=Rp*$9Uh~ 084TI 9U.81OUOh~7\LOwwLvGjCj=<B)l4iPpe uoMs3|?Jds$P2mJY`Eq\H=Uw:i*ssCw/IG,BAYy@X,5@v|&"<IM=N ZPD=%A      %  o_Y)yqw7 KCL;#<QU*nuRUbi,Jm3)R `9tNe !-!A#y$$1%HP%R%E%w2&&='|)D)G)#*-<+Wj++,*O-dz-f-hF..q/) 050I0?0 141.2K@3:303:3344B5#5Y5 U6v7_7?7!*8L8Uj88Cq:B::9};C;Q;M<=+=i=;>2>v>k?F?>6@`u@g@>AhAcBeYCGCD?DTDM(E{vEtE/gF%FFFG%GHJ^HKL>YNONNAxO$OCPH#Q&lQbQ=Q4RGSY^S)S4S<T)TTS~T7T2 U=U:VtAVXYzZPL\x\]]N^O^57_m_N_l_b=`K``apb$d8dVLddnd/(elXeye?f:hBjEkvllE*npno>p%rk"t+t2uw?z/=~m $0JO+ΆD|DG UuQ]A HKN?n*َE!+ @8yOa7ɓVJ8FʕܕuB*muUiuq7:ow 6ϜOoRܞş3j<[۠7#);΢ xw Iͥ[զ1I[ާ =A3EyRQ?)N Joa2ĹPܺ-Gݻ%0'w=/A=)$$NQsLſrm H{P^*M;G57(m36')*<*g((*-2`&z4" . F P [gv6.I(x%.53,:`##1+H]+< 3S6l"!*20F0w.2 2=WqI.:+i.-+?&Pw"'6)`"*1F%f8)GYL! "#*Nh % ( :[wK3e2%#B-f * !+L:1$&1#7 [|# ,( =5!sIj 1xL+#6H]sSE&*94R3 ##9']%&9 ;$#`& >([g .4L4c"   )<D;<; 6C ]i9(((?!Z|l.eG^Yda:;4=rA4@vD]XIEA.E7}'[!Eg'i(o 1:55p-?"!7%Y=&*=.$l3" ,2;_% &# -'L&t/* $%<b)!I?e+21! $S 9x ' - &) 'P x  !  "  )< &f , , ! '  &1 :X & ! &  # ,C -p # ! ( "  0 L $k 6 ' / ( !H j  1  # ) H g *| ! / $ * -I w #  8 " . 6N  . 9 $ B2 9u $ . C G (^ # L ( ! A ,]   > & 2# 0V    '  6% \ 5x : F /0 %` 2 " ' / .4 %c ) + ' 6 +> j  3    "9 *\   @ E 2G ;z = $ . &H o  # $ ' *  %K #q  1  & $, *Q )| " * + ;  $\    ( 5 , (D m )w # 5   6  -W : 0  $ 0, #]      7  2 z C )K u 1 $ #  ) 'I "q 6 = :  'D Ul  #   - G h 8 ' 5  4 E "N %q  & ! ,;! >h! ! ! ! ! " 5" #E" i" }" 1" " -" # '# &?# f# J~# :# +$ 0$ N$ U$ n$ $ $ !$ $ $ )% ,,% "Y% |% % % % % & %#& I& T& i& & 7& <& 0' 6B' 9y' 8' =' 4*( 9_( I( &( 3 ) >) ]) 4k) ) +) 5) #* ?* K* g* C* C* F + Q+ g+ z+ + + !+ + + : , H, &`, V, (, )- N1- 4- I- - . 9. M. m. '. . . (. / !/ #B/ $f/ )/ / 7/ , 0 90 4F0 6{0 +0 /0 )1 (81 *a1 (1 -1 '1 2 2 #62 Z2 e2 z2 2 2 82 2 12 '13 Y3 n3 ~3 3 3 3 33 %3 4 )74 a4 &~4 "4 4 04 )5 B5 a5 p5 5  6 1&6 "X6 {6 6 6 6 "6 +7 /;7 k7 07 7 .7 7 !8 648 k8 %8 8 8 8 8 8 9 9 9 59 $9 9": \: < 0< 3?< "s< >< C< 5= O= 4_= = ,= ,= > +> D> !d> > +> *> 5> (*? (S? 6|? "? ? W@ dA |A <A A QKB B B #B "B C 1C "CC fC nC C C C $C !C .D FD 6E nE bF ]*H HI I fJ J "J $J %J K ,K &AK !hK K K K K !K $ L ,EL rL )L L L L )M +M GM cM 3M (M 6M #N :N VN `N 9N %N ]N ?O ^O %qO O O O 'O 8P &HP 7oP P P P P Q G1Q ,yQ Q $Q Q Q #Q R +:R QfR ER R ' S !4S /VS S ,S ,S "S )"T BLT %T "T T )T U >-U /lU U ,U U U 9U 70V 'hV 'V V V V (W *W /:W jW )W "W 4W X #X !CX eX Y 3#Y WY cY vY Y Y Y Y &Y  Z /"Z "RZ uZ )Z aZ [ 5&[ -\[ 0[ [ #[ [ )\ !2\ T\ #`\ \ \ \ $\ \ !\ ] 5] M] "a] ] *] ?] ^ ^ -^ AF^ ^ ^ &^ ^ $ _ !._ P_ &f_ (_ _ _ +_ 0` &E` Ll` ` ` .` a d Vd (ld d &d d d e e 6e $Re &we e e e e e f (7f 2`f f &f f f f g 4g Mg eg zg #g g :g 5 h &Ah 1hh h !h 'h h i i -8i fi ki #i i $i "i j ,j n On QDo Fo (o )p +0p $\p p )p p =p +q Kq Wlq q -q Cr 8Rr 2r r $r (s !-s Os ns s s 8s s s .s .t D9t ~t +t t (t )t )u ->u lu E{u u u u v v $5v Zv uv 'v "v uv Vw $#x )Hx +rx x :x &x y +y 7y Iy Xy ty y y ,y -y 8z ?z Nz Sz cz ~z z z z z z z { !&{ *H{ s{ { { { { -{ *| 9| Q| k| 8r| 7| | | } } *} #B} f} 3} } -} #} ~ 1~ O~ a~ u~ ~ .~ +~ ! * !K #m    #  ) D c /|  8ǀ  > R 0` ! 0ρ & =' e  5 !Ђ    0 E "e    Ճ !݃ , C, p  4 ׄ &߄  ! 6 P l 4 ) !> ` ) % 1χ   C. !r   $ /׈ & ;. ?j ) 'ԉ 3 *0 [ !| " # )  ! 1 F _ 4 ! }֋ &T *{ $ ˍ + # (5 ^ 'u    Վ , ,* W !q 2 !Ə !  , (K :t 9 4 >, $k  =Б ' 6 W n ے x ) * /  , (M )v  # !Ԕ ) ' #H l   ' 5 ( F 'c  ! ͖  O 4Y $ &ԗ ' # D M l z   Ř ט : C' k + ! Ι ,  $ B ` u ! ' ٚ   - J D`  .    : Z j  . 9˜  $ 5 +T  8 Н  " '1 Y -r ) 1ʞ # . O 2p ! %ş 8 2 i5   Ҡ   2 8K  ( ȡ     h8 8 6ڢ 4 $F $k  / ! ܥ , ' )G q "  &Ʀ ) 9 Q h  ! %§ "  ( 3D x '  ¨    0 B b    !̩  / $= b u  " Ȫ ۪ - ' B a z , ī #ث j g $ ' &D 4k # ĭ ԭ  $ >! 1`  Y   5 YI  %    ( 3 @ "` ? ñ  $  7 T @p  ˲ &  " 9, f    ȳ (ܳ   95 7o & δ \۴ 18 j  ( ̵ ֵ -ܵ ( %@ 0f ? ׶   ,( U a z  7 ڷ  + < M[ N P 'I Kq  (ֹ 9 -9 g 'w !  Һ +  +< h   +    . J Kf 9 ! , 6; r % ) ӽ ,  " (9 b H TȾ T 0r ! %ſ  #, "P #s  " * 3 6, >c #  4 E $_ !  "     5 S 5n  @ !  ,- Z /]      ! $7 \ g "  D * $$ I a } 0 4   $ D=    # 4 O9   6  " !* L l    %    & M1 M   #  )" CL        + J ` t  +   $ 3 "J m  %    ' 9< "v    # 7 >4 s  &    / A /Y '      ! 2 ? ] n }  ( [ La C + < #[ # " - 6 *+ V !g 2 5M I 4 + 9. <h 3 (  4 H Z k {  G 6 & %F Vl A  & 8 jM W V g _2 , V W Ob _  2 8 9 [O * 1   ! =A " A 0 &6 6] ! > ! . 3F z  . &  " 17 &i 0 = * ,* "W z  . E 3' )[ / %  < 8 S b z   5 * '# $K )p s  2 6I   O r s # "/ "R (u - < ( #2 V p    5  ; "T "w 8 3 0 %8 ^ #} S ) 4 )T 7~   ' (  9 6R < I + W< !     % -> &l       ) B "[ ~ 0 * %  .5 !d $  #    . "? "b # $ '   # 9 R 1k C   !5 0W )   : $7 \ } 4  # ) 1 K W &p ? !  & /< l 0   : W v - ( + (: c  !  - ( /% $U z  "   2 #2 )V - ! ! 5 &( &O v ( ,  '  " 0> Ho C & # E9 # 2 "    ## G c {  ) 0 % /  3P  "    . %* #P ,t 8 "  (  4 N ] &p  &  4 *  &8 _   (  N M U c } &  *   " (B k    # &   & D K F[   ' , =( f y # .  ' #% 8I .  4  A X q #| " # # ' )3 ] z + & $ ( &; b 7~ + -  - $7 1\ / ; ' %" !H j t  '   0  "< !_ ? , 0  !2 T (p w w + 0 &    " 4 "G !j  e c u ' 0% 'V /~  (   . -H v  &   #  . E W o !    ) +  7 J k - '    $ 8 L Z w    -  ( f@ @ = & dG : % 8  F 4V 8 ! N s5 - +   :; v   ' % / 1,! ^! z! ! ! ! 1! %! :" &T" 8{" " 0" " #  # #?# =c# )# (# #  $ $ #9$ *]$ 1$ )$ $ % % 1)% [% d% "% $"& G& f& & #& *& /& 1' ,M' $z' e' *( 0( 'M( u( &( ( ( ( (  )  ) &2) Y) p) ) %) ) ) d) C* W* h* &{* * .* 0* ;+ T+ p+ )~+ + + $+ + A, 7- B=- $- 7- - (- ). ;D. %. !. . ;. !!/ $C/ h/ / (/ #/ */ *0 ,I0 ?v0 *0 ,0 1 $'1 0L1 }1 1 "1 1 )1 2 2 2 S2 1r2 52 %2 *3 "+3 N3 &i3 #3 3 3 3 3 83 % 4 F4 'P4 x4 4 4 4 )4 ,5 ?5 Y5 8f5 5 )5 5 &6 (6 /I6 y6 6 E6 I6 JD7 7 938 m8 -8 /8 -8 -9 C9 \9 "x9 -9 19 '9 #: +: 4: #H: l: $~: : &: %: " ; '/; #W; {; 5; "; ; < .< L< +l< ^< $< = #<= "`= = = = (= 5> 1:> 9l> :> > ? ? %? @ &@ ,D@ +q@ $@ '@ '@ )A $B -kB 'B 1B B +C '1C "YC |C +C "C C .D "0D &SD (zD 2D &D (D &E #AE eE #~E E E 8E ?F %QF wF 1F F F G G 9G RG iG G G %G %G H #H &:H aH lH ~H 7H 3H !I #)I MI iI I <I I )I B J <OJ J %J $J "J K -K $IK #nK %K $K K K $L "-L PL ;lL L L L L L L !M %>M !dM FM KM AN ![N B}N N %N &O ,O JO #jO 3O 'O *O >P +TP P $P P "P P P / Q #:Q ^Q ~Q !Q +Q Q $R &R ):R dR pR R 1R *R ,R S ++S 0WS S ,S S S S 8T _JT %T T -T #U ,BU XoU U ;U !V @Y 3Y "Y +Y 1Z N4Z 6Z Z Z Z " [ -[ 0N[ [ [ &[ &[ $[ \ *.\ Y\ "z\ \ \ @\ !\ ] .] wM] .] "] ^ (2^ >[^ ^ ^ ^ 8^ /_ G_ 1c_ 0_ +_ )_ ` 4` Q` /m` ` ` ` ` a a 8(a #aa a a )a La /b $Kb )pb )b &b $b Ec ?Vc c c &c c d q"d 'd %d d 2e &4e 5[e >e e &e f *f vDf -f )f +g ?g IVg g g 4g % h 61h hh Jh Ch Ui lj &rj #j j j j k $!k .Fk uk k k k 7k l >)l hl 4l l (l l )m =m Tm sm Im m m "n 5+n an {n "n n #n o 4o To so ,o !o 4o Kp ebp p 2p !q { X{ r{ #{ !{ { { | | /| E| #c| | | !| #| } } "} C} P} %g} -} } 7} F ~ @Q~ $~ 2~ ~    ) F ` {   $  " #2 &V !} # À  - # C W w L ́ 0  ,2 _    6˂ 8 .; #j 3 ƒ Ճ    / E c w   ф  "  6 $N s  A . + %C i ~  @ $ - #: +^ % 1 5  8, 1e , 1Ĉ R I 6i 5 ։ # 2 1E 'w ' ,NJ   :2 "m ' & #ߋ   80 $i - !nj   ) ;; w ) &    /+ )[ " % Ύ #   &; ,b ) # !ݏ ) ) ? ^ h n w   @   86 #o  * 0ґ  /$ 3T 4 @ 4 33 g 5 & 4ܓ & "8 5[ ' 7Ɣ   (, !U 5w  B̕ " "2 =U 3 -ǖ 8 Q. 2 A J @ ʘ 1L r~ * & AC ( = ; -( \V L @ 2A ,t a 6 D:  9 )؝ 5 !8 GZ = * 4 .@ +o - ɟ 6 ( 3I 0}   ˠ g wH # " r 9z 2 3 H Rd ' ߣ rǤ +: ef K̥ 5 @N   +æ # "4 *W ; ( # - +9 3e  5 & ( 17 Ki 3   / @ \ v z '  ˪ ު & # &Ӭ & A! Gc 2 2ޭ  E. [t Ю  7 7D I| =Ư A CF / + C M* x   Nű * ;? ^{ Zڲ L5 3 ?   & 9 AJ \ ; D   0 K ^ } *  ܶ    6 *E 'p  ( *շ 8, e <j Zu о f    7 O 5$ Z m DJ C [d ;  + -: h  V : 4/ d 8 EC   "   5# 0Y 9 @ , :2 +m , ) - ' +F r 2 2J 4} ) ! $ )# !M o  . $ / ! #7 [ =u  1 A .= 9l J ) G 2c  - 0  +- !Y { 1    3 ,I v . % $ # F0 'w +   3 0' -X ? )j *     9/ Pi }= ^ [ v e 8r D U U  C _  g |  D 3 *4 _ [ | | f_ ( %  = ] y b _ h S m 5 4M  Q > 0 0) Z v  ?7 Ww u M O  Q U a' S L "* 'M ]u 7 q  W} a M7 : ] 4 )S 8} h h < B V D_ : J Z* D m 78 4p H , g B N " M8 0 4 G 84 4m b C I Z ;% <a > 7 $ F: h e PP 3 Y :/ ,j - + 3 8% 8^  H 3 6 +; 8g ) V 4! GV G a rH O M  Y G E7 } -% 3S 7 V _ bv I K# Ao C f \ X .6! e! /" " j$ '% % z& w ' ' ( )) -+* Y* x* S+ t+ , - - tq/ / {0 61 1 2 #3 s4 X05 b5 5 6 q6 F8 BD9 [9 M9 1: %; 8< ^> |@ RA 0B 2PB %B 1B -B  C =E E 2F sF 0G LI :@K {L .vM 0M 2M # N '-N 9UN oN (N n(O O BR =R S ( T 2T PT qT !T T A@U 7U V 6W -W D!X *fX SX ,X Y UY V"Z <yZ [ bq\ ^\ 3] ] ^ ^ M^ (_ 0!` /R` 2` ` `a 4`b c Md d Sg g Th h li 'k :k l bl l ;n Tp Zip "p =p L%q 9rq *q Eq r r Hs t u u :v w x ^y Hz O!{ Bq| 5}  % k L ։ [f ‹ g z yi  < ܓ  b  Θ gm ՙ VԚ + c l Xu Ν s[ yϟ nI e e ^ .  *  ; \ } D b] l - ) = 2 1 ʩ nҪ &A h + <H ^ C ٮ i ` I Bг  D  F X   1 h M 4l   b 1 1C 5u K m  k  G g( { t # ] } X W lL ( ] $@ e @ 2 /  6 Q hq G w" t  R   0 a S = %   9 3 pO `V ] 1 G 2T & 3 ) ) +6 %b u } *| Y = '? sg  ; X <Y [? ? W> #) XM  6 m ^j  c K  ` }+ 3 [  n b_ F     } u ~* T m} z  + ) | aP  D   $t  r  d S ]Q  ] @   q r (s   _ j! ](" B" x" uB# # 9$ $ % P& _' o' _ ( *m( ) r^* * + k, - #. v/ he0 z1 #I2 m3 4 5 6 7 q8 (9 9 :`: {; < "> #? 7? @ A RC D "F G pG H H TXI J DK K KO W?P P %Q kQ n*R qR S S tlT eT 1GV yW |X /YY jY *Y Z nZ 3R[ \ Q] p ^ +z^ )^ ^ Bm_ a Bb Gc &d 2d 2e (/g =Xg Og g h Bi @j 3j ] l gl l n bo c%p Ep (p p q 1Vr Kr Sr (s $t dt v Zv Z(w _w \w [@x 'x x hz z e{ { | | k} =8~ v t Q ` 4L K }b ;  F  5  V s & IɌ G G[ G 6 (" K @c E F 21 Xd 2 X pI ( Q P5 = iđ i. X I F; L aϓ 41 xf uߔ TU N ] # (+ (T F} ė <ؗ  X > w2 ] 3 T< ` V 9I x 6 ~3 ] [ nl m۞ _I 6 R 3 G: 1 w L, &y 2 >Ӣ j q} ?ߤ  d" a 7  0 Aȩ C N k z  g F Gd L - 3' *[ % 4 ) E NQ 6w  y w 4 m w+  e  u [*  =  +  =2 p   ] ]5 HY  #  f , +& R r" / 1 + *# N X 34 +h  s n r *j ' ~ * ,  0 ? # ,$ Q  0 a R %  O  [, + 6 * ? <V 5 ( y )    2  p H y f Q W  < > \)   . c 8@ y !   Et  L_ ; < % A # O  VL [M @  zf t V H @: !{  F    | m (  )[  = w B _ 6Q c ! n" d" .[# %# <# O# =$ h% n% & & ' m( ) ) ?+ g&, , G- xf- t- T/ 0 70 y0 Pk1 2 S3 4 44 ,!6 oN6 M6 7 7 f8 V9 : : \; kH< < = > 0? ? A B C <C C kD E =E &F G G 2H I tJ 5J dJ ,K K ,L .M Z P BeQ Q R 4S T oV V W IW 1X 5X (Y Y Z [ mi] ^ y_ ` ` a b Q7c Fd e ?gh ph ?i Xj $k `*m ]m 0m Ko <fo hp r zr Ks cs Vt cu v Ev v Dw EDx Qx Tx s1y fy ! z .{ f| o7} } S~ ~ _  B S   Z  l 5 -K 7y - ߊ 3  r( Y ג 7 >/ @n . /ޓ 3 6B 1y i  S [1 Y is Vݙ ]4 . 8 C .> m Y s  * M2 , | +* V - - d )H r cw ۨ Te  {˪ G e 1  ˫ '  / K a vu : & 8 2U "  1Į / 0& 0W  I = 9. h ' , 9ݰ 9 +Q }  1 F X' ] ޲  E T B ? O a #{  &  ' B( :k S > L9 = DĹ + Z5 : <˺ I 2R . h 4 HR = Eټ = C] 3 gս ;= y Mn ! , m q EL   e T 6 4V ,  I C    D ` r P y DC ] Ok J\ Aw ? Z T D DG ^ v b t F O OB * , [ :F $ K   * %  6 4K  / *   $ 0  X  !- O   |)   g & s  H E U 3 2@ >s ` 5 I n q #} d E kL  _    disTW 6%N->%  f } @  2. Sa Z   &  - !:O\' Uz#!_>B[8=ve9*=[x3Xa ,I>U 3v-\E{`e7& `!!x"",##m# f$p$ $$?$v$a%_&()h0))*( +I,y^,{-LT.e.f/5n/?/J//0B0/Q00071 1>3>.40m44144 5(585 Q5[5 d5o5~5555 55 55 6)"6 L6X66j666w7738]829O9R:Kr:F:;,;=(9=yb==x>>>>-9?g?il?U?U,@@/A?A~Ai`BB[C.yCC(C#C/C%.D.TD1D!D6DcErFTG2GE%HQkHFHFIKISI[I cInIuI}IIIIIIIIIIIIIIIIIJ JJ$J 7JAJ#PJ tJ#JJJJ J JK)KcBK4KK"KL%-L.SL#L#L(LLM?MVMjM?M M M M MMN.NCNUNfNyNNNNNNN'N+N )O!JO#lO*OO#OIO=P@P2IP&|PPP3P1 Q!(]g]*~]*]],]^e4^2^+^&^ _4_%Q_-w___,_+`.3`?b`*``-`!a88a0qa(a3a&a)&b/PbZb:b(c8?c:xcGc)c-%d%Sd%yd3d3d(e0ee$e(e!f ?f'`fOf%f*f")gLg5bgg.gegMh>kh=hh h hCiIi Xiej}j0>kok1k^k" lNCllmmnoTp'p)q8qPqJiqGqq-r9BrL|r?r+ sG5s3}ss'Htpt,tatu2uGuNcu!uUu)*vCTvGvVv.7wBfw'w@w8x6Kx8xPxQ y+^y/y'yVy9zIzc]zZz{6{{C{|>|N|&M}t}g~w~!~"~~Bh34+;g U /)")Lvya0W?mXNUs8ZŅ9 2ZjC<0VE͇;߈'0C#t2ˉ6Q6N܊D+1p:@݋*%I~oET4ΐ6b0fvk!IIkA~ܟ{[נ#pâc19 V>w0:7"0Z9'ťE'3[!x(Mæ*<*Y$##ͧ82*-]. Ȩ+ڨ-"+P,|4ĩA;L_v5_ 4֫/ ,;h\6b<d-k<۶p,̸SعePzh˻m4iW|9>x4bC{]bq= >\]B2 NngqDRBCU`dEb |nCD/othsMEXE>#N8dMSzB Oq1lfWwEcQ){EW  Ck$:d202cAZe3?l=Fcr{Hs8~w[+>V>p=D;PD]+1>Ip|5/WeWCgYCx~mGW"7;Z>U+D1X&u:z0kP[hjN/a~: )=Ww2<C4(8aoI )   ' b M!ojfPWrKy HRcP Z3aM.@RTrx=Rd S KI!b!!"ug##$`%f0&'hP)){*-C+q+ ,",;-2-1'.fY.E.$/K+/w//7/1//0o133$;5"`55m67o7=9:G<<o<m=3=T= >&>.>6>>?Zw@I@?B\BWCCC$D&D/D7D 5FBFG?G II xJK,LLL1M@KM0M(M2MN)0N<ZN:N7N O'O0OPODP LRWR:S<SSSS.SS>T`TTHT:T9UU_VwV>0W2oWWWX YZZB[)[^(\&\^^^*^^8_yL__tTaja4b>Jbd"d2ffSgR.hhD j PjB^jj5k#lm nnTpspOrSrcrVvrr,rs+s 1s SL$ Ȫ?iiQӱ%ڳb`õiI[5 gWroKM&!dq0p >0cxtl:|#Y$}yIf4 ,A+nX=P> / F*/54: d&n8mhNfW 6;6 CWW1L~i/_yR,TXF9uB`9>}DNq,{ 47>v'Y#(0&8G_e#, k:2qZH9d]jp9  " *  <  R ]mf] (sGR*<M"pxLb$).N}J+vMv1 !$ !%!!"""q$'$($$$%MG&'4)O)4*+6, :,G, b,*m,,L,-- - -M=-X..0,0?0"12'2{3k4055 A6N6l6 66u6778,8|93k:P:^:VO;!;3;1;-.<!\<!~<}< =+= J=k=:==;F>u>>?_@ BCIDFzF4G@G0HH1I/IJ;J4KDLZLhyMM(NNGNI%OEoOKONPPP,Q@QqRS:SSTYU[U5VLVBW+HWtWW6WWW4W4 XBXMGX(YYwY9E[>[[}] ^_X`abkcdgd,e f~g7i^0j~j/m>nnoEp{qwssu0:v?kvvawxyuz{%{| }E}8~=Z8)\"06TSqŇ7O3A1/?Q7D(|2.؊\:dN0ʍ0yƎ@<ؒn7|A^_>Nf+^"3)t.L9*Jjjա,^+:Z 5Ŧtp-7ԬW+(Xʯ#lo²x2T9,1+@nLlc~XH</l~bjepq;Wb=4Z'NevH%xnQ,7xm@_@<<qyEj^ /~YP 1')?.ng)ad-&!)LRdjTyT'"W % Ni 0?6.VSbU`Nv ZSOS4Qo',T5|FVm~&!3I[ v=2A6#Rv  ;  # 37 k ~ & $  9 #  2 < P W +t    :  ! 9 !O q   0   6 $L q           NI9#2=FpMl-XR=9HR  Sk!!S">"`'#R##8#u($k$& %1')ZY**7++D;,, --8p.i/m1511H334<55p6C'7k7R$8Iw88}p9?9%.:sT:s:q<;;G<|<F]=X=N>hL??DI@@7A?BBKDEGVIFJG?KlK9KQ.LLQM?gM$M=MM PXPJQ^QxQHR%gSS}WThT>UU~V6WW6XPXVYHmY#YYceZ[Z-%[ S[a]aIab{iccSd=e0Ve f5gUg!h95hHohh{i jkVmnn6(oO_oPoipzjppqsO;tFtlt5?vsuv,vx-xtxxVyoy?z{2{{{Ex||@}y~]9>$OcVW#kSpWD܄!!Cpa҅OJ7= KGW_֊69Cˌ>nYpoϐ?v_J֒!IX<T|~'%#Iiy<y-IQ |[?؟XAqV+ o6?[ݣw90:8.V\FE)oR5W3R:"(^]DAUxNDzKS ]x)7ڸa[okB۾"m9z)x[}::d0.1b`N7,d|_"PlIE`[}?d>S)}[1@/MB==J  V+.<^BI[F&wX5<yE6z}; ISk5 =YN#z#D?\2/l,DV%##8@\   ? Z b G5SsTpt:?BAUdI-w5>gG )!(/!QX!P!j!jf"""#E$$y%&Q 'a['W'(9(H*);s)#)/)+*)/*Y*2m*;*0*0 +5>+t+!{+7+.+),#.,4R,,+,!, , , --+-$?-d- x----J-.+.6Z./.@.D/HG/?// /&0$)0*N07y0[02 1I@111)1(1:2>M222=2B2C@3=3>3 4; 4 H4U4o44!444"4 5$5ZD5555@526 I62S6)6-66465'7]70y77/7'7?8+Z8 8)81899"59X9-w9&9N9:&2:>Y:m:;#; A;$L;)q;(;";(;<1+<5]<"<,<<2<.=N= 8>CY>$>$>">3 ?>? \?)}?? ??#?.@ E@Q@Xb@=@8@*2AI]A1A,A!B!(BJB `B.jB2BSB& CGC`C[uCCEVD_D3D0EEEZEsEEE`EOFdFiFF6F5F G G(;GdG#xG#G'G%G&H95HoHNH*H/I4ILI_I|IIICIj J tJ0JJJJK?K&_KKK:K-LM ,M6MJNMMMQMT9NN!NNNN= O)JO&tOO'O%OOP4&Qj[QQQhR4RzUtjVqV\QW8X1X-Y_G\I]]m^k_Vq__N` `T`?a5Fa#|a)asa >b_b'|b&bbbvc0|c c cccC d#NdLrdVd=e]Te9e2e:fOZf$f>f5g\DgCg,g'hL:h9h1h6hU*i3i.i4i2j%Kj3qj1j9j3k*Ek.pk+k&k8k7+l0cl6l5lWmFYmm=mAmA>n9nOn) o*4o;_oBoAo- p)Np,xp6p4p3q3Eq/yq7q9q/r4Kr0rLr;r-:s2hs%s9s(s+$t3Pt(t8t3t,u(Gu&puOu2u<v;Wv:v8v2wC:w6~w@wFw8=x'vx?x5xDy2Yy<y@y0 z-;z!izdz4z2%{FX{-{:{J|9S|_|I|?7}Dw}g} $~=E~0~h~97W%9%%C;/GE1=+o)4Ł3R.>AFRI=1ڃ> .K9zAA78?pA=N00',؆?.E/t23ׇ7 9C9}RS B^HR/=Am9)+.?*n2D̋+)=(g<+͌<:6AqC20*.[J3Վ+ 5Q3gC,ߏ*  7*A*l>֐D:IL8ё (#0L$} ݒ  =Tk/ ͔8ה5$"Z2})ʕ'-CJE@Ԗ.`D %՗4 !BdTy0Θ:":]t3}9($&93`%8L@/T#""˛(*'?/g7&*&"QhtCݝ0! Rs{$""ݞ#!$F9L9( #'#Ko3 ޠ%:BF}/ġ@E5A{E4I8V*٣A)Fp80:>)5hϥII7LΦ!8#Ko#I2 T@&2];Mk-)#M)d%ƪ63"N$q"+%J =V @=B =c10ӭ2075h/ ήۮ' !-CSn1;ͯ4 >Zl u:'&8?,x85ޱ,AA<5,#(-L?e8-޴, /9,iC<ڵ4.c.v'/ͶD1B(t!ҷиY'DEl~9<ɻ.X5RA#C5y=;ս(:$R!w15I>b=<߿7T.":<LZ g%,- !%5[*c*612ddAU0((Q,h+* +(&"Or3L)l$.9'4$\F'1 8?)x #G/wI2.!H j1.15Tf&!X7D|"  ($GE^;5#%2I|06(-+UY.1[K8"59@DH:.%-7eB$8# 5D+z5$-J, D8}!&"- (Nw92',nE[79O +(.C"Ru-# 0Ji(4I@,O-|O.5d"%+3C]-x='S "`7 !#EXh*;2!/QbQ|+*1%Wp0-&#4N^#{&"&(;"Ps/=)FN"j$$/-]=sK664k (09&>&e/$"4Qi!$-(;BC~EDMVp %?e$3  7 HVNp?'$',LNydi-_12)4\/;!D?/*U5+S_B@")c(*) )!FhIp:R%x8:9BS<N1Pe"$!)'&Qx 436*j P3% BNbq<=TE  ,;R%i -1)&P`u7, )X4[$ 3>$W|9 1' 9 $Y ~   # : 0 %K $q % &    $; $`  "  3  :, g Az  7   #  4 2B *u D  9#Tx #%#9Ig!o,I8;t'|*$0<!2-T*4K(c#A1'-NUZ.1.4`7+ $%?)e">"?b0,!&N'u481 =,Z /C`&yA)$ 18I;?I DWG&' +3F_.%  1 !< !^  2!1N!3!:!!$ "*."@Y""*".")#(0#&Y# ###3#6 $,B$o$%$$'$'$!%T<%4%.%#%8&BR&$&&#&&& '1'O'e'C'T'(03($d("(1((-(-)$M)!r)&)-))(*0*FB**N**6+F+c++#++++1,DA, ,,&,5,-P6----(-*-".0>.,o.?.0.< /0J/:{/!/*/ 0<0N0Q0,0 1)1E1-`1F1:1%2562l2222+2y2;e3@3U3084,i4G4>6.7,L7?y7)7678 18!R8(t84868 9%!9G9$b9$94919':K;::/:!:(: ;,;'F;n;&;0;';"<$<3A<$u<5<.<<#=4=%L=r==.=;=>$%>0J>[{>>C>|8?? c@)n@!@&@D@2&AYAhA}A(ASA1BFBscBBB CZ#C~C,CCCC1D<.E%kE(EBE+E)F&?FfF"FFYFG$7G.\GG G8GGH&HBHVH;iHH#HPHS9I,II{I0IJ%zJJ1JJ J6K;K8LK K<KWK$;L`L%zL4L LLLMI,MvMM7M/MVNXkNVN2OTNOO1OBO70PhP+|P(PPP8Q"=QB`Q$Q"QQ9Q8RTRcR~RRbRHS+bS8S7SS1T9ETT4TTT/T+UJJU^UbU1WV'V-V?V2W.RW-W1WWW5XAOXDXCX'YBYA_Y]Y/Y6/Z6fZ+ZZ"Z[[$/[T[:t[[I[% \3\<L\\=\$\,\$]C]Y]p])],]]$]2^R^Xl^2^,^%_&A_h_>_E_% `3`*S`X~``*`a.:a)ia=ada'6b^b]zbb,b*c)Ecocc!cc-cd6d*Rd#}dgdk e"uee3e e6eV.fff!fff g#g27gjg#g+ggAg-h)Jh,thh1hh( i02ici-i.i3iAj&Vj#}j!jj&jHkILk.k$k.kl#9l]l:{ll6l>mGm)bmmm(mmn&n@nVninzn#nnn1neoatoQo0(pMYp1p1p+ q57qFmq4q q/ r~:rCr8rV6sDs<s<tCLtHt*t u4uEuWuiuzuuCu5u#v!?vWavKv!w'w%:wf`w`wn(xx`zyyz]{hu{X{`7||ON}B~:~t.6  %>6/uC9 %C?i Hʁ"66Wmł 7-;#i<):DN5,Ʉ,#%=4cJB*&BQ6!ˆO=[l '5++G(s-ʈO@X9Ӊgl.&% 03<d9)ی#) G(h#&6܍&:.Z.B9851n,(͏a'X>1. 62;4nIݑY'iD^0.Γ $/<&lǔ''/"Wz%<ؕ1.G"vF+* $7-\/*7*Q3|-ޘ!) 3QApD+="[9~,˚'' FH0)*>T!p;,Μ! +/K["ʝ73SAs+' #@4&u&Bß4/;=k5%ߠ%#I7f4<ӡ/,@m!¢8ڢ61)h '5ۣ&'8`&w(Ǥ,Ϥ56elBҥ%;OS$-Ȧ+"<'T#|!ʧ+3$L2q9%ި$)AP5b&$0E![},%&@,Q ~42&*4_1|^ˬ *4E(\D.ʭ?9X&vٮ!&C SaT& +4-`Iذ%&4?t8*ƱGC9 }@ɲ!ز>9 W*e,'. &5\${-.δ3514gJ+.1,` $B2B2+u*6̷$>)Z*#CӸ#.;XjJùKZ-m++Ǻ':@,{ļ#"@y`sڽN4E8[6˿9߿98P5 . /%="c#&4F@\=%%2>Iq,%&-Tt!%2%X vva[p'lWa.P89RrV*UGw10Gx%B  !4A1v;="?Vh z@GS4e;- -#N8r9*):Pf'~@;?#$cB)- 5T#t(31*'oR4$1-N/|-5E {'  y%7/>K;=$)-;i#ZKCL#2/,0K]$$L(^:)-.2I>|;;F3/z9#3:<w:#-$-*R"}42'80$i$+% :LB0 *&#7![0}3 ; F,b*(8:YIwMN^:+M2y5?7"Zu#7:=&d mw", %.82g?'(:+'f''&E8Kw4'1%Y%$86;:Ev;7B0s)t9(4/:d.5'0,(]$- 2%;X,;(E&l+,,& =2'p&4*5,UAE/ :,Z$*"BF]1$1#-%Q w#" %>'d6%$&5&REy?8)8$b"?$B;I~(% (34\#2-+8B{ .)F"i|&""1LTQ?"3UV&(.!+%M.s1>7UK:3 3+T >" !3-R(4 ':JJ=8 ," 2O  2 % 9 "* @M w ' . 5M ( + a : RP -  / & =9 w 8 !   )*/gZ[)9McKKI8h=2"25=h}7$\x$,; B$M,r54 -$5R%)J+,X g:'#b +;(D7T3055F0|+*= #^! &D&Ip +f!A)c;7(&*KQ; &7$P|u'1!L4n1@O*f)*v 1z . 8 !X0!!*!5!/">6")u"["V"R#$,$+%K%[%y%%(%<%+&3H&4|&&E&'C('#l';''(' (#*(N((g("(S()$)(A);j)!)")$)#*%4*(Z*?*'*#*3+-C+?q+<+w+"f,7,-,+,9-?U----%-.-\+. .B.K.8/4W/O/q/#N0Hr0@0|00y1+11<1$/25T222222)3-3M3$f33L3'3+4K4-`4444"4Q4 K52X5 555!5+5+6J63a66!6 66)7#:7&^7777"73878O8j8/8888%8.%9T9e999/909:74:"l:/:$:!:.;(5;^;&z;);;;*;*<<<*W<6<<=<T=Nc=6=?=)>,H>u>~>>>%>&>#?)A?&k?-?+?'?*@4?@#t@@/@&@ A"A BAYOA(ACAB45B!jB)BBBJBI+C?uC-CAC%D?D ZD2fD4DD'DE$'E#LEpEEE&E%EF)&FPF#lFRF<F0 G%QGwGG#GHG$H5&H=\H8H%H5H5/IeI9yI1I*IAJfRJ(J:J5KSK'cK5K5K(K( L=IL#L)LVL%,M+RM-~M'MMMBM1BNtN'N+N"N%N( OEIO&O)O&OP%P;P:YP.P*P,PQA7Q+yQ#Q"Q-Q.R%IR(oRARR#RS &S 0S =S/KS0{SGSS$T75T"mTT,T$T#T=U8\U:UOUJ VGkVV9V& WC3W2wW+W@W1X IXJTXXX0X,X7+Y%cYLY#Y#YBZHaZ:ZQZa7[L[B[[)\\];]t]*a^(^E^4^B0_=s_B_f_R[`f`Ra2ha]aJaTDb(bJb) c67c(ncNcBc=)d<gd3d0d1 e!;e=]e0eDe:fLfQfjfnff&g1ggrmh\h2=iDpi]ij+j}%k(kkkI8l9l>llm20m/cm.m.m1mP#n2tn0n:n<oCPooHo3o3.p<bpPp;p ,q#7q<[q-q"qq q3q!+rMr$ N<  ;z{w y?=$ < ]Q .<# l 3%z+2 E Ly LSTY c YR="^_[ { {H @ `' Vp !  \*  H>kEP bK N  sx1_L1 I 7 &l/ u[I E1TA;<"wCSq }ai1 / 6}i !  0ct+` y>& f'l (AM"jR Tf u 58  ,M  k   !f \I @ C2N y@ /3m$oV|T =V{_  M| { / u&,  a $ rF mqglh] M 0$Aj 3  9# ?  UJ| s@H wS Cfv p^+msv . G<) 2 C :   `8 F6 4\09R\_  W/8 : '  h  H,p  )  / 8 , .: s  FjKW   @I ;V YL 4_i / > J F6dX a ;x 5 +Hgw  2oIDf(c *L  1F  J t 0EF9  \0FS+A|: B Z  3 n Gt o  J =U  BA f2v}l{Mh D p$ w _]EVCOA9 ^J  W ni x 5o | & oQ { (v VZ ? 7 q\ > *#   j  %  8l  17   8dwT A s(^ ? =  % \ U9 T_(y>Z@ m , e j%j o#( $`4  oK] |{p w 8^ k -U8kSf /^  '.)^*afQHw {DS  Q< 7d Qj^Xhk  R %A?  >.e|~ r;  kvszZ  r /UOM \  GX yU Q< 2 D8E<xT! + aP )b  ! >j| y NE! -@)   @bV + C {r :_Q81 _  X  SB  XI !  I& ^=u ug 4 6 JW pWG }$Q "u!j'?{ n wd  7A ;j2 )f" ut [ 9  X  9I } = Z H>l'!F | GD^@:( }N4|aNqb $ O9&Y0 &(I[ m } < # REtoHi B :3 u. \   G ^ka wX  # T }  sn Xx `J h \@5cp  xY 5Js[:5\ a   4_-4 to w 1 2WI  ;iJ / f Yb+0 e Y!LN  A3 V4 ]w M  17?MO Edgy/Fi   %  0#N  D >T ) k #*&* H a gL D < < # + {:@P Y ] icZx l  1eqN [u&XD a A~ VkR kq ' q~| Q *9 BG;m9&"0u~ j ' n8  reg Jx MR n U;Y-&?z b[i ,i$w0a <dz4M/  IR3EL"  N[c"jI  5r   62=zO 7 fP  7+ cE i=@Z % z QJ n 0 3&f k  -m4Q6  dgJs: U s -`n .f @ ) 7AbeKYj  b 9TMlMN6I~ q { + ]y n M i  Ch8]"H h!X$ n FB6p t  p% d ^' 6 u d  W 5Al } <iO [ pU m   # S*O  ?q,; s mq$  , zO< ! w-y<g P  yXN pLL_ _ . (Q  {pF Q w <%#K w 5q0LgNM T N #r Yx^ n  . G &`RWC+- Y>4J()AK n6x2> Bg, \Y *2dv ^^ Y Fe2 ~{]e. Ws: 1 1t jG?( 6 +czm_ , H 3  ~ Wi= ~}=Q ? )) v( ~%E >GX ^)m f  aG N4 7*  F WaT+  zB9 SM S D P z - |" %{ 4 JLs  P\ k  T Z# )b\JWd# `WJn + hp  6 iD ^  o Ci  :  I y2]/  ! b QwF .Lfa -3m C g? ]n jmd *0; k_%&*L 9e 53l2K   K O5  ?7fz  X7 ' a ,=l5 ^z d] @ \c? -M9j * P > Z EG g ;h mz<8 k%c 4 D L *G Aq  t )> Fk) &"  : O 'n [ 25 m/  v[!K P'M A cq`  /BRa>@ctKc| > cqm %{; c G 8G k-mV O ~ O~ `oTl (hr Sv / |/ ]z0^O#N "BIq5 }a zD s9'6YE  &5 ]e& u & ?zj t$N 1 $g E *IE( e ) q v) pNTC wA eN+k{  y(6 ) o! q 4v%  - e &IZ O`3 h Bb 1pS8X  lu ee `3hB %3 r Qy ? Q  g ,2 _ eF K@  gDW  f  )k L b4  -S/+ <*m? (hh>=<@ K*VGX 6DC.2R Rk!" U }  8'Ap#; Z . A U'kgNk { & `$nDq"2x ZO $ .&~Q QOL~r )cGk0 n QK7 el]  F/p% r6t>~a Z6 1@ Z 3PC ;rH X-[]?n ] G w% # 2  u m [3 Xl   W ls f4c d$ s 1%` O  x  i, E: ` !j }/ : nZ 7O H1~  _0 -BX va+\p Ju  5 4>Ge _  Vj9D.X"v O";   V   | ?6 P (s fL 6Uol Z nZ R o jW;03Z5 1 z ( *Q)5 gi\] Gl  [ HxbK9 a   ( . D7 P fLZa  ` a V8 r  +  KU = \A r  :V- p5 =u L W RCW ZuBn ! :/ r8 IJ=ut = F 6 * s y@* y (  T^V}z FH 'dW { [)=bgJX   . 4VY7"_9 a, pR  K R~bH)Y$pbhr HS w&  & " Fi9.C dN+ D?= []8 Qp @o8SCvZ31[ kYm- ^ 2g  = f \ BY %r Gf<URi't l rnY v,gT >     HOG t! } MU4 D; 4 t *F }:V p R9hOr / TEs*U` H !T;\IAf  `G }}") =\ tWx :`\zc  x _ T l*2D S <sD  G B e.{#>;l?<y 9[Q 6;~S[ @ '< cNHz$ 5 2& N =~   xi'e' A S& `3VZ \c " : Uc]9   8P" s BL7xP S o H>IUyud ! w&]C^Hh| E [m 3\(   v$ O p#e C# hIY Cx  w M 4+< ZB Y ']  2 ], "r. V v }M| x? z sPb9   hM ;tvb%" / GY ~ .^o { JI !BtJ1P &z K j [PRw 7 ( $ A  <C x >t.K :XRNa 4 mI+ $rHI# C 8 voK=HU?si L @\ FD} 3 ty@y T  r- @N  q2i8 xN#   0 $j W78 +  vS, cb1  C  FTA _b `7F }.X d  6X D~r07   `KB 6J P^[E8 '6*tB [  0?   T6 Zu 6i<  o pDX q | -$ ST'R e+ugi<u  Y#? q K@( 7 r  C mX ~ _ # vaFI!!1o  EU e 'h"T- H ogy4P |  1s(   > X{ M?_\ 35q  K C0b  U  5|J3E_vx  e +#.1  qsh   V  > 31 2;oD  0]0 1Bk v `P = 7^SnO 5_ ,W ~ t}  K J 0V{Dv, 7 y ` ~ V, EM/% k RH > 8w"qM 4Y`p7?ch  Pa "3E-cAC9  Ko W -jAGug n 1r/KKx.## = b, B $, C S ,( :    f .' l/ QV2 )T ']%|nV N, EL Gs 9t  ;Q | PPc4EL2By 3eu W :F{nb}K   !uxd lg9mM5 -o $V%( Y J B b  S J E B  }$kR 5e  |` jLb7 m g !hw z / :[{    v9 F _8|P Bo I;  l L =_ U- - [%Pq5y  +%h 0 q:O U }c ,RL  )dRo OtA.g ( @^;= 0  'Hd ;O :Q :z P) W P }CU f| 6dd t]h"  y  Sl ,jMJ45 S U* im| , x~Ou~> j+fD~* dUd Zb r!yw 30  W Rvh [ *I - xd z%ZM@7 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 (truncated from %d to %d lines): diffstat: keywords written to %s: use 'hg help -c %s' to see help for the %s command [space] : (un-)select item ([~]/[x] = partly/fully applied) A : (un-)select all items up/down-arrow [k/j] : go to previous/next unfolded item pgup/pgdn [K/J] : go to previous/next item of same type right/left-arrow [l/h] : go to child item / parent item shift-left-arrow [H] : go to parent header / fold selected header f : fold / unfold item, hiding/revealing its children F : fold / unfold parent item and all of its ancestors ctrl-l : scroll the selected line to the top of the screen m : edit / resume editing the commit message e : edit the currently selected hunk a : toggle amend mode, only with commit -i c : confirm selected changes r : review/edit and confirm selected changes q : quit without confirming (no changes will be made) ? : help (what you're currently reading) $ 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 [press any key to return to the patch-display] [push] pushvars.server = true 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. content 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 'orphan()-obsolete()' -d 'first(max((successors(max(roots(ALLSRC) & ::SRC)^)-obsolete())::) + max(::((roots(ALLSRC) & ::SRC)^)-obsolete()))' 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----- A value of ``messagedifferent`` will append a ``committer: ...`` line to the commit message if the Git committer is different from the author. The prefix of that line can be specified using the syntax ``messagedifferent=``. e.g. ``messagedifferent=git-committer:``. When a prefix is specified, a space will always be inserted between the prefix and the value. All Mercurial clients should support this format. All Mercurial clients should support this format. The compression algorithm strikes a reasonable balance between compression ratio and size. 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 By default, servers will ignore `--pushvars`. To enable it add the following to your configuration file:: FILE = MERGETOOL Git commits have separate author (who wrote the commit) and committer (who applied the commit) fields. Not all destinations support separate author and committer fields (including Mercurial). This config option controls what to do with these author and committer fields during conversion. If available, the ``zstd`` engine can yield similar or better compression at much higher speeds. If this engine is available and backwards compatibility is not a concern, it is likely the best available engine. Only supported by Mercurial 4.1 and newer clients. The --pushvars option sends strings to the server that become environment variables prepended with ``HG_USERVAR_``. For example, ``--pushvars ENABLE_FEATURE=true``, provides the server side hooks with ``HG_USERVAR_ENABLE_FEATURE=true`` as part of their environment. The default is ``messagedifferent``. This engine will likely produce smaller bundles than ``gzip`` but will be significantly slower, both during compression and decompression. Use this compression engine to explicitly disable compression. With the default settings, zstd compression is both faster and yields better compression than ``gzip``. It also frequently yields better compression than ``bzip2`` while operating at much higher speeds. ``dropcommitter`` will remove references to the committer. Only references to the author will remain. Actions that add references to the committer will have no effect when this is set. ``messagealways`` behaves like ``messagedifferent`` except it will always result in a ``committer: ...`` line being appended to the commit message. This value is mutually exclusive with ``messagedifferent``. ``replaceauthor`` will replace the value of the author field with the committer. Other actions that add references to the committer will still take effect when this is set. hg children => hg log -r "children(.)" hg children -r REV => hg log -r "children(REV)" 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 pushvars can provide for user-overridable hooks as well as set debug levels. One example is having a hook that blocks commits containing conflict markers, but enables the user to override the hook if the file is using conflict markers for testing purposes or the file format has strings that look like conflict markers. qguard foo.patch -- -stable (negative guard) qguard bar.patch +stable (positive guard) qselect stable * Release note 1 * Release note 2 .. directive:: title ... :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. Consumers wanting stable command output should specify a template via ``-T/--template``. Description of the first long-form note. Description of the second long-form note. 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. Note 1 Title ------------ Note 2 Title ------------ Section ======= Section 1 ========= Section 2 ========= 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. There are no backwards compatibility guarantees for the output of this command. Output may change in any future Mercurial release. 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 changed lines for every committer hg churn -T "{author|email}" # 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 more information about the repository status, abbreviating added, removed, modified, deleted, and untracked paths:: - 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:: - stabilize orphaned changesets so history looks linear:: - 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. It abbreviates only those statuses which are passed. Note that clean and ignored files are not displayed with '--terse ic' unless the -c/--clean and -i/--ignored options are also used. 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 -t/--terse option abbreviates the output by showing only the directory name if all the files in it share the same status. The option takes an argument indicating the statuses to abbreviate: 'm' for 'modified', 'a' for 'added', 'r' for 'removed', 'd' for 'deleted', 'u' for 'unknown', 'i' for 'ignored' and 'c' for clean. The -v/--verbose option shows information when the repository is in an unfinished merge, shelve, rebase state etc. You can have this behavior turned on by default by enabling the ``commands.status.verbose`` option. 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:: You can skip displaying some of these states by setting ``commands.status.skipstates`` to one or more of: 'bisect', 'graft', 'histedit', 'merge', 'rebase', or 'unshelve'. [commands] rebase.requiredest = True [pager] ignore = version, help, update [pager] pager = less -FRX [rebase] experimental.inmemory = True [rebase] singletransaction = True 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 feature # send all ancestors of feature bookmark hg email -b # send bundle of all patches not in default hg email -b DEST # send bundle of all patches not in DEST hg email -b -r 3000 # bundle of all ancestors of 3000 not in default hg email -b -r 3000 DEST # bundle of all ancestors of 3000 not in DEST hg email -o # 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 - "+n" is a linear run of n nodes based on the current default parent - "." is a single node based on the current default parent - "$" resets the default parent to null (implied at the start); otherwise the default parent is always the last node created - "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. $ HGPLAIN=+strictflags hg -R "$REPO" log -r "$REV" $ REV=--debugger sh -c 'hg log -r "$REV"' $ hg --config web.allow-push=* --config web.push_ssl=False serve $ hg log -r"$REV" --keyword="$KEYWORD" $ 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) (deprecated, see :hg:`help config.ui.editor`) (deprecated, see :hg:`help config.ui.merge`) (deprecated, see :hg:`help config.ui.username`) * Duplicate items are automatically ignored * Items that are different are automatically ignored if the similarity is greater than a threshold. - 'strict': push is abort if another client touched the repository while the push was preparing. (default) - 'check-related': push is only aborted if it affects head that got also affected while the push was preparing. - :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`) - ``--tool`` option - ``HGMERGE`` environment variable - configuration of ``ui.merge`` - ``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" - `base` to checkout changeset and apply further changesets from there - `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. --flagname=foo --flagname foo -f foo -ffoo --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. ``--tool`` option 2. ``HGMERGE`` environment variable 3. configurations in ``merge-patterns`` section 4. configuration of ``ui.merge`` 5. configurations in ``merge-tools`` section 6. ``hgmerge`` tool (for historical reason only) 7. default tool for fallback (``:merge`` or ``:prompt``) 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 :``readsize``: total size of data read from the disk for a revision (sum of the sizes of all the blocks) :``largestblock``: size of the largest block of data read from the disk :``readdensity``: density of useful bytes in the data read from the disk :``srchunks``: in how many data hunks the whole revision would be read :``rev``: revision number :``chainid``: delta chain identifier (numbered by unique base) :``chainlen``: delta chain length to this revision :``prevrev``: previous revision in delta chain :``deltatype``: role of delta / how it was computed :``compsize``: compressed size of revision :``uncompsize``: uncompressed size of revision :``chainsize``: total size of compressed revisions in chain :``chainratio``: total chain size divided by uncompressed revision size (new delta chains typically start at ratio 2.00) :``lindist``: linear distance from base revision in delta chain to end of this revision :``extradist``: total size of revisions not part of this delta chain from base of delta chain to end of this revision; a measurement of how much extra data we need to read/seek across to read the delta chain for this revision :``extraratio``: extradist divided by chainsize; another representation of how much unrelated data is needed to load this delta chain :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.logencoding: Specify encoding name to be used for transcoding CVS log messages. Multiple encoding names can be specified as a list (see :hg:`help config.Syntax`), but only the first acceptable encoding in the list is used per CVS log entries. This transcoding is executed before cvslog hook below. :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.committeractions: list of actions to take when processing author and committer values. :convert.git.extrakeys: list of extra keys from commit metadata to copy to the destination. Some Git repositories store extra metadata in commits. By default, this non-default metadata will be lost during conversion. Setting this config option can retain that metadata. Some built-in keys such as ``parent`` and ``branch`` are not allowed to be copied. :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.remoteprefix: remote refs are converted as bookmarks with ``convert.git.remoteprefix`` as a prefix followed by a /. The default is 'remote'. :convert.git.renamelimit: perform rename and copy detection up to this many changed files in a commit. Increasing this will make rename and copy detection more accurate but will significantly slow down computation on large projects. The option is only relevant if ``convert.git.similarity`` is greater than 0. The default is ``400``. :convert.git.saverev: whether to store the original Git commit ID in the metadata of the destination commit. The default is True. :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 backref is either A bookmark named '@' has the special property that :hg:`clone` will check it out by default if it exists. A changeset that has been "split" will have a successors set containing more than one successor. A changeset that has been rewritten in multiple different ways is called "divergent". Such changesets have multiple successor sets (each of which may also be split, i.e. have multiple successors). A changeset that is made obsolete with no successors are called "pruned". Such changesets have no successors sets at all. A requested view of repository data is displayed. A successors set of changeset A is a consistent group of revisions that succeed A. It contains non-obsolete changesets only unless closests successors set is set. 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. All string valued-elements are either strictly alphanumeric, or must be enclosed in double quotes ("..."), with "\" as escape character. 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. As described in :hg:`help merge-tools`, Mercurial examines configurations below in this order to decide which merge tool is chosen for specified file. At the end of the upgrade, the repository may not be readable while new repository data is swapped in. This window will be as long as it takes to rename some directories inside the ``.hg`` directory. On most machines, this should complete almost instantaneously and the chances of a consumer being unable to access the repository should be low. BUNDLESPEC A bundle type specifier. These are strings passed to :hg:`bundle -t`. e.g. ``gzip-v2`` or ``bzip2-v1``. 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 Mercurial's behavior changes very little from release to release, but over time the recommended config settings shift. Enable this config to opt in to get automatic tweaks to Mercurial's behavior over time. This config setting will have no effet if ``HGPLAIN` is set or ``HGPLAINEXCEPT`` is set and does not include ``tweakdefaults``. (default: False) By default hg journal only shows the commit hash and the command that was running at that time. -v/--verbose will show the prior hash, the user, and the time at which it happened. 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 files known in the first parent context of the working directory are examined. Use file patterns and/or -I/-X options to limit target files. -r/--rev is also useful to examine files in another context without actual updating to it. 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, rebase connected non-obsoleted descendants onto the new changeset. Use --no-rebase to avoid the rebase. By default, rebase will close the transaction after each commit. For performance purposes, you can configure rebase to use a single transaction across the entire rebase. WARNING: This setting introduces a significant risk of losing the work you've done in a rebase if the rebase aborts unexpectedly:: By default, rebase writes to the working copy, but you can configure it to run in-memory for for better performance, and to allow it to run if the working copy is dirty:: By default, the first bundle advertised by the server is used. 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 .". By default, this command will show which locks are held. This includes the user and process holding the lock, the amount of time the lock has been held, and the machine name where the process is running if it's not local. COMPRESSION The compression format of the bundle. e.g. ``gzip`` and ``bzip2``. 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. Can be overridden per-merge-tool, see the ``[merge-tools]`` section. 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. Close the connection to the server. 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. Completion extends only to the next path segment unless --full is specified, in which case entire paths are used. 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. Display paths using a slash (``/``) as the path separator. This only makes a difference on systems where the default path separator is not the slash character (e.g. Windows uses the backslash character (``\``)). (default: False) Do not attempt any read operations on this repository while the command is running. (Both repositories will be locked against writes.) During release notes merging: During the upgrade, the repository will be locked and no writes will be allowed. Each ``directive`` maps to an output section in a generated release notes file, which itself is ReStructuredText. For example, the ``.. feature::`` directive would map to a ``New Features`` section. 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``. Elements: 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. Every ID must be a full-length hex node id string. Returns a list of 0s and 1s indicating unknown/known. Every ID must be a full-length hex node id string. Saves the bundle to the given file. Example values: ``COMPRESSION=bzip2``, ``BUNDLESPEC=gzip-v2, COMPRESSION=gzip``. Example versioned ``.hglfs`` file:: 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 HTTP transport, the stream will still use zlib compression for older clients. 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()``. For the ``chrome`` format, default is ``0.999``. For the ``hotpath`` format, default is ``0.05``. For the ``chrome`` format, default is ``0.005``. 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. Given an output file and set of revisions, this command will parse commit messages for release notes then add them to the output file. Given space separated file names, shows if the given file is ignored and if so, show the ignore rule (file and line number) that matched it. 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: Here rev2 has two possible (i.e. divergent) successors sets. The first holds one element, whereas the second holds three (i.e. the changeset has been split). 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 However, detecting stale locks may not always be possible (for instance, on a shared filesystem). Removing locks may also be blocked by filesystem permissions. 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 --rev was not given, split the working directory parent. If --working-dir is used, files with uncommitted changes in the working copy will be fixed. If the checked-out revision is also fixed, the working directory will update to the replacement revision. 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 given, the template is processed as a log template and applied to the given changesets. Otherwise, it is processed as a generic template. 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 SOURCE is omitted, the 'default' path will be used. If a URL is given, that server is used. See :hg:`help urls` for more information. If STARTREV is specified, only those heads that are descendants of STARTREV will be displayed. If ``--source`` or ``--rev`` is used, special names ``SRC`` and ``ALLSRC`` can be used in ``--dest``. Destination would be calculated per source revision with ``SRC`` substituted by that single source revision and ``ALLSRC`` substituted by all source revisions. 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 `name` starts with `re:`, the remainder of the name is treated as a regular expression. To match a name that actually starts with `re:`, use the prefix `literal:`. 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 section has long-form notes, sub-sections will be emitted:: If a section only has short-form notes, it will consist of bullet list:: 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 depth is specified, the result only includes changesets up to the specified generation. If directories are given on the command line, only files in these directories are considered. If merge tool is chosen before matching against ``merge-patterns``, this command can't show any helpful information, even with --debug. In such case, information above is useful to know why a merge tool is chosen. 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 arguments are specified, the repository is evaluated for upgrade and a list of problems and potential optimizations is printed. 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 files are specified, the commit will be pruned, unless --keep is given. 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 pager is set, Mercurial uses the environment variable $PAGER. If neither pager.pager, nor $PAGER is set, a default pager will be used, typically `less` on Unix and `more` on Windows. Example:: 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 first current parent will be used. 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 no view is requested, the list of available views is shown and the command aborts. If not set (the default), built-in defaults are used. Run :hg:`debuginstall` to list available compression engines and their default wire protocol priority. 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 revisions are specified with --rev, those revisions will be checked, and they may be replaced with new revisions that have fixed file content. It is desirable to specify all descendants of each specified revision, so that the fixes propagate to the descendants. If all descendants are fixed at the same time, no merging, rebasing, or evolution will be required. 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 ``FILE`` argument points to an existing file, that file will be parsed for release notes having the format that would be generated by this command. The notes from the processed commit messages will be *merged* into this parsed set. 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 repository is configured to use the sparse read, additional keywords are available: If the source repository has a bookmark called '@' set, that revision will be checked out in the new repository by default. If the update succeeds, retry the original operation. Otherwise, the cause of the SSL error is likely another issue. 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 pass a revlog index, the revlog's DAG is emitted. If you list revision numbers, they get labeled in the output as rN. 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 ``pushkey`` and ``pre-pushkey`` hooks to control bookmark movement we recommend you migrate them to ``txnclose-bookmark`` and ``pretxnclose-bookmark``. 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 addition to the features disabled by ``HGPLAIN=``, the following values can be specified to adjust behavior: 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``. In most cases a changeset A has a single successors set containing a single successor (changeset A replaced by A'). In normal clone mode, the remote normalizes repository data into a common exchange format and the receiving end translates this data into its local storage format. --stream activates a different clone mode that essentially copies repository files from the remote with minimal data processing. This significantly reduces the CPU cost of a clone both remotely and locally. However, it often increases the transferred data size by 30-40%. This can result in substantially faster clones where I/O throughput is plentiful, especially for larger repositories. A side-effect of --stream clones is that storage settings and requirements on the remote are applied locally: a modern client may inherit legacy or inefficient storage used by the remote or a legacy Mercurial client may not be able to clone from a modern Mercurial remote. 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. Large repositories using the *generaldelta* storage format should consider setting this option because converting *generaldelta* repositories to the exchange format required by the bundle1 data format can consume a lot of CPU. 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. Lines beginning with ``#`` are ignored. List changes in files, showing the revision id responsible for each line. List of available views: 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. Locks protect the integrity of Mercurial's data, so should be treated with care. System crashes or other interruptions may cause locks to not be properly released, though Mercurial will usually detect and remove such stale locks automatically. 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: lots of HTML content sent by the server is derived from repository data. Please consider the potential for malicious repository data to "inject" itself into generated HTML content as part of your security threat model. 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. Older Mercurial clients only support zlib compression and this setting has no effect for legacy clients. 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. On some systems (such as MSYS in Windows), the terminal may support a different color mode than the pager program. On some systems, terminfo mode may cause problems when using color with ``less -R`` as a pager program. less with the -R option will only display ECMA-48 color codes, and terminfo mode may sometimes emit codes that less doesn't understand. You can work around this by either using ansi mode (or auto mode), or by using less -r (which will pass through all terminal control codes, not just color control codes). One use of this command is to make the next :hg:`status` invocation check the actual file content. 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. Only non-public and non-obsolete changesets can be `phasedivergent`. (EXPERIMENTAL) Only sections with defined release notes are emitted. Only used by the ``stat`` profiler. 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: Otherwise, the changelog DAG of the current repo is emitted. Output can be templatized. Available template keywords are: 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``. Release note directives can be either short-form or long-form. In short- form, ``title`` is omitted and the release note is rendered as a bullet list. In long form, a sub-section with the title ``title`` is added to the section. Release notes are defined in commit messages as ReStructuredText directives. These have the form:: Render help documentation. Repeatedly prompt changes and commit message for new changesets until there is nothing left in the original changeset. 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. Results are displayed as follows:: 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 no locks are held. 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. Runs any configured tools to fix the content of files. Only affects files with changes, unless file arguments are provided. Only affects changed lines of files, unless the --whole flag is used. Some tools may always affect the whole file regardless of --whole. 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 commit` for more details. 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 scripting` for details. 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 also ``server.zliblevel``. See pull for details of valid destination formats. See pull for valid source format details. See the security note above before enabling Git subrepos. (default: false) See the security note above before enabling Subversion subrepos. (default: false) 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. Server operators may define custom keys. Servers advertising "clone bundles" may advertise multiple available bundles. Each bundle may have different attributes, such as the bundle type and compression format. This option is used to prefer a particular bundle over another. Setting HGPLAINEXCEPT to anything (even an empty string) will enable plain mode. Setting a lock will prevent other commands from changing the data. The command will wait until an interruption (SIGINT, SIGTERM, ...) occurs. The set locks are removed when the command exits. Setting this option allows server operators to make trade-offs between bandwidth and CPU used. Lowering the compression lowers CPU utilization but sends more bytes to clients. 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). Similar to :hg:`commit --amend`, but reuse the commit message without invoking editor, unless ``--edit`` was set. 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 Unified Frame-Based Protocol Frames ---------------------------------------------- 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. Stream bundles are special bundles that are essentially archives of revlog files. They are commonly used for cloning very quickly. 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 -c/--check option checks the commit message for invalid admonitions. The -l/--list option, presents the user with a list of existing available admonitions along with their title. This also includes the custom admonitions (if any). The Git importer converts commits from all reachable branches (refs in refs/heads) and remotes (refs in refs/remotes) to Mercurial. Branches are converted to bookmarks with the same name, with the leading 'refs/heads' stripped. Git submodules are converted to Git subrepos in Mercurial. 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 ``FILE`` argument controls the output file to write gathered release notes to. The format of the file is:: 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 ``graphtop`` query string argument can specify the starting changeset for producing ``jsdata`` variable that is used for rendering graph in JavaScript. By default it has the same value as ``revision``. The ``help`` template will be rendered when requesting help for a topic. ``helptopics`` will be rendered for the index of help topics. The ``ignorews``, ``ignorewsamount``, ``ignorewseol``, and ``ignoreblanklines`` query string arguments have the same meaning as their ``[annotate]`` config equivalents. It uses the hgrc boolean parsing logic to interpret the value. e.g. ``0`` and ``false`` are false and ``1`` and ``true`` are true. If not defined, the server default settings are used. 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 ``revision`` URL parameter controls the starting changeset. If it's absent, the default is ``tip``. 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 (``-1``) uses the default zlib compression level, which is likely equivalent to ``6``. ``0`` means no compression. ``9`` means maximum compression. The default (``3``) should be significantly faster than zlib while likely delivering better compression ratios. The default behavior of this command can be customized through configuration. (See :hg:`help patchbomb` for details) The default naming mode is "identity". The description of the DAG is read from stdin if not given on the command line. The dirstate will be set to the files of the given revision. The actual working directory content or existing dirstate information such as adds or removes is not considered. The exact name of the destination archive or directory is given using a format string; see :hg:`help export` for details. The extension reads its configuration from a versioned ``.hglfs`` configuration file found in the root of the working directory. The ``.hglfs`` file uses the same syntax as all other Mercurial configuration files. It uses a single section, ``[track]``. 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 arguments are special: 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 following sections denote available actions. 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 journal is used to see the previous commits that bookmarks and the working copy pointed to. By default the previous locations for the working copy. Passing a bookmark name will show all the previous positions of that bookmark. Use the --all switch to show previous locations for all bookmarks and the working copy; each line will then include the bookmark name, or '.' for the working copy, as well. 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 option is unused on other formats. 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 order of compression engines determines their priority, the first having the highest priority. If a compression engine is not listed here, it won't be advertised to clients. 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 sparse read can be enabled with experimental.sparse-read = True 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). The value may contain a special string ``%nonce%``, which will be replaced by a randomly-generated one-time use value. If the value contains ``%nonce%``, ``web.cache`` will be disabled, as caching undermines the one-time property of the nonce. This nonce will also be inserted into ``