=U#@!A!c##4ͅ3-6-d.ֆA'(iT5t3ވ& 3Na*‰ "?Ziz   Š"Њ'.-H4v+-܋: 4Ez8 EYٍ;0R(/,܎: -D'r+Ə24Ր) .4$c/#Α- .:9i>)G 2T-0ϓ+!Jl3,.0%_$#FΕ*)Ts9ƖWwm(+K_ҙ242ܛ4/֟O]VNA"E'hZM39Xm.Ƥ7L-:zD?5:@pJrGo,J4/Ld*Lܨ.)6XA7ѩ: ;DYcڪ:>2y:)&?8ExCH1KF}6ĭ/&+R3./DDt\nDOʰ@A[0MαXLu6²ZTT'ѳ̴n!$"׷ոϹ׺xhlhiҿC[@=^3=hA:RP!h33..+!Z|*/](P[y}(Js !~:sDS,Gt{P(yos>Y"|](wWmxR-mH@p>j #/$2MZi[H[wX,cj4^^_];'!2Rpq h|8/*Ks b8W~sz N     . psaK)N{.>l(^|  yP!!"H$?%YV%&F5'|'(( ) *<*b+u+c+ [,5h,(,2,1,$,-%Q-&w-F-6-).'F.3n.!.4..//0<o11T>22!33|455k5Mb656t7[8 9[9A<:V~;;~g<l<S=r>>??hs@f@CA/BBCODEEXFmHG^GHHxoIIJeaKKLa]M<MmM;jNN.OMOs-PFP PQRST3U$EVjW$XYYcZZZ[\]"^_a``&azab{bjcvncocxUdzdqIePe fff:ggYh3h)!iKiikqfl:lm,mmoRQppVqflrosCt@t:uu+CvEovv>wbw&yyz{^}13''[PԂ\c_UXۅj܆GCՇP7j8.9gO-}/^V& 4*7_'9@J:!>>3%CYCE=';e5\גB44wY\?cDE,Õ9*->LlE7B7CzHfTn\ØK dl7љ- 67-nX؛T]p#_ƞ?&fe(mfz~d+ҩwv{9#p+ձw[ӳiUTָ4޹W4s̼(@7i8~ڽYj|ix#B_:hF=}_?9>~x>6:RU0.eeX-1v]r?:|AQP[?y`tyZ^IH3x#Hi$zc;?t4}pBuHP`WC6N,XB]}yN=(Af-kJ1|3V#5> \t  1  Wh  P`  j}*ohhAAHIBmh_]Tmn x8{3X!b!\"#%&'-( (3)  +s,.7.>.\/|/j/rg0S01.1.`181C1. 2;2235L"6o7{77w880w92909J :=W:9::':,;D;:X;9;;1;F<Ff<<7<u="v>%??B?V!A>xA=AFA/[G[V)]7]#]>]^~4^^*^6^+_B`*```!``gaatbddxe$|ehe ffcfq,gg%(hJNhh[i riivi"j8jj!klemT~mmmppq6er%rNrsst.uuuv_w2vwSwZwXxxx xxeSy4yzzt{{_ |8l||p}}}0}B}7~*V~~x~/aHɂp>W[3-&TX pfUׅ"-Pa,&mB ?d_P h)% hLe[D5?<J|ǐ/֐d5k(%ʒ  **3^ gq ԓݓ 61P5WɔS!*uM-C:07h,U 0*7=mLKښJ&UqUǛmjio"**%6FO ȠРؠ&.6>EM S] f !ʡ ߡ !I,` !ʢ!"$G W7c   ȣ գ    $ /=W`ir{0ѤԤ10"Skͥ-/3D*x")ڦ$+)&U%|-(Ч+.% T_vF Ϩڨ)()<*f'&ө+%& L&m Ȫ*! 6@],n:֫*>O_p13Ь#5Yp#ڭ6Lbs*Ю'>"Q't%¯ԯ2&K*r"++6Ronޱ5T+qI,+0\)x+ &<'W>>ش((@+i1ǵ"׵*5F|3(϶7)0Zi{"*ط 0<.[&d!R"4uME$>;c+)˼>4DCa&k5&Ⱦ)},Ŀ4ڿ9AI'<J T40eR..7XWk0& 8Yk%!4eVew"* >4%0Z;&$$E8#~##1%+B ny%-)*8T1*LS\Lp9yscB+at.\890.M_Q~:~YCoW5oIC[e;UnS=>U?775;ho2RAR%<x0W=>X|tKa).A R>^yuk37%]ja= E=6FEu?TBAgTA I"&X%Flc n~[iD'   ,8 Ie   o @_^z 0B+nD+Gp9#;nPt <43+<hq"xe0_ #w!!!!Jv"e"D'#hl$F%7'hT''''?'M8(#((w)rF***!***P+,,]--.+/+//-v0'010!0( 1I1R1* 38K33>3^3B64/y44,5!>5`566758s8LX99^; c;n; r;);@;;1j=7=e>:?R? @ ABBCCCh>D<EEAE-F"G$1HVHIIJJJK+KAKXKnKK#K K;K LL$LM MMNUO ZOfOmOO O OO\}PP~RCTTaV0aWW7X>X YYZYEZ dZHrZZr[[([[ >\.L\B{] ]]]]] ^"^1^ @^OM^^5_`mbBcSde(ffJiggBhEh";i^iBdij/skk,k9k!l $l$Eljl(mE;n}no]qDrTsvsMWt9ttOub6v vwyTxxyzC{|}g}/} (~@3~jt~~GI;*@G'uoL2FȆ|>;>DS-׌$+Ȏkˏ7;|#m4C'^PגLp>}z|GFėJ nV@ŘA=H ˛_ I+Up ٟ^c%gAZޣpT=u:N^Rd4ȫS#-i=13ٰ s%1W#&4[984*mv1,^)+UZ r} +ȺC]+M@ysnlO/<}l "-HQpWBKKi,*& 4S`rK1rQv[uw5Q*#3H- 8kr+Ib~&?f-v5==Uj;K ]!k=vw%Z_NlP2 ANBx_61Dv[-j{'%MPl,##6 P[Xv'&YWwv)+UGf2C4vxf9Vz+ (7`vaW=T(#"7mZ(QE  } %  w> ~ S5!N*_X>7qvht;4/n&@g A 4K5t| ] O"\T"="Q"A#Q#@$n$I%T%uP&&*'. (<;(x(rT)D)r **++Ca,,,l3- --/-n-N..\/EM00002M2234445f6!7=779Y:;/;>;;P<!U>/w>S??TA$ABf|CCXDG&EnERF~WFF{G4aHH#I&IIJ$J*JIJ!fJJ JJ J8J2K;8KtK(KKK K<K$L@L ILWL3iLLL#L L9L'M 6M@MRM#YM}M M6MMMM N)NCN*^NNNNNNOO3OPOcOlOsO4yOIP9P2Q.RQ8QQ-Q)R*0R%[RRSST3UUOVDW7/X=gXBXX4Xj1YYe2[v]t^P^^j_J_K@``evaa%^d2ee`tfEfsgHg=gwh:hNh*i,CiDpjYjykk~Cll5xn|n<+q7hq%qqAs tt*uvkwx7xLxKGy#ygyz;zuzRt|UO jYā_)Sʄ2eх7,ކB 1NE6w|}DGJ-UcӍe7h)0?D4W/I0:7Br#Zْ4_H?U>B~9CMۗ)IkItlK+3wv">@f&mIhG^?U*NuϢ/E%u&>S=HЪ&c@EYˬ4%7Z2ŭ:ˮzx\ձNCObKEes0MHQNw"F2y#k9MIT+9S$xQM,kKZ|;H\O{?* 6EV +7J7)C!#x6.SO3q[xLyvRI[x:3L~SCS$NXJ`S2W@/)$=QbLrmt HIr;G5@(v36' 2*E*p((*-;i&4   )5DUs.%.553k:#*#F1jH+"5U6n"!*20H0y.2  %0Jds..,>k|"6=]"z*%#? V` ~ %(E WxLf#42#-4 bo* 11#2V,o(=!%>ISr1 B U j       # # '+ %S &y 9  ; #. R i y   > . ' > [ s 4 "       <4 <q      ,%(R({!l.eeG~^YdA:;4RA@VD=XI%AE]'w( 5;"q!%&= $^3"# ;' %c  & #  '!&/!/V! !?!$! "+"F"+c"$"'" "-"&+#'R#!z#'#&#:#&&$!M$&o$$#$,$-%#1%!U%(w%"%%%$%'#&/K&({&+&#&!& '7'#S')w''/'$'*(@(#`((8("(().6)9e))B)9)$/*T*(k*#**,*+(+D+&]+'+!+++ ,&,:B,=},2,.,--)K-+u-'-6-+.",.O..h.&.$.*.%/#4/X/*x/"/*/;/;-0$i00(00(0(15=10s11$111)2:21O2$22)2'2"3'53U]33 3#334#44C45x444 445$595T5o5#55)5556*6@6^6e6~6 666)6,707P7i7777%7 7 88":8]87u8<808699R9894999<4:&q:6:3:; ";+0;5\;#; ;;;; <<;9<u<&<I<<=D8=}='====$ >)1>[>7z>4>6>+?/J? z??#? ????@#@82@k@1@@@@@3A)8AbA&A"AA)AB1BOBkBBB B"B+B.+CZC0tCC.CC6D =D%^DDDD DDDlE$E E0E"E>F5GF}F F,FFF!G2GIG+ZG*G5G(G(H"9H\H HIlJJ"JJJ"JK,K!IK.kKKK K,K&L!.LPLpLLL!L$L M 'M5M3TM6M#MM M N9*N%dN]NNOO'/O8WO&OOOO#P,)PVP lP#xPP+P'P Q/*QZQ'yQ"Q)QBQ"1RTR)gRR>R#R/ S`f`-}`` `#`` aa3aEa]a|aa(aa1a4(b8]b3bbbbbjcqcc"cc!c,d 1d ?dMd<kdd(dd1 e =e-^eCe8e ff8"f [f.ff fDf f+f)g-EgsgEggggh$hAh)\hh&hh hhhi !i/i,Bi-oiiiiiiij%j=j Tjuj!j*jjj kk/k-Gk*ukkk8kk ll#7l3wl-l'lmm-m#Dmhmmm.m+m!n 4n!Un#wnnnn#n o3oNomo/oo8o p>p \p0jp p!p p0p& q=1qoqq5q!qq rr:rZrzrrr1rCr%s;s4Yss&sssst$t@t4tuv!*vLv/av,v&v;v)!w'Kw3sw:w*w: x Hx!ix"x#x,xxy!y6yOy/oy!y*y$yz++z(Wzz'zzzzz {,{L{2f{!{!{{{,|(;|:d| |$| ||=}'P} x}}} } } }~~)~*~'G^!|)*) 3Nl0('+!Km$ ΁&'> ] iw+! #4Rp!-߃ 'Aaq.9+1)]? Dž,Յ !#EH`{ۆh186Ӈ4 $?$d/!Պ, )@j"֋ !%G#_'Ō3Ed!э$(F"X-{Ȏ^@+]"'# $>A1̐Y%i(3? I$]Փ 9-F7_(97Q& 1 1 K%X?~',-J xF7 D_+z9Ř--I+Z'ݙ!,76d%)Қ, ?K(bHT!F#h"#Ӝ"* 346h>$ޝ!%AYp5@!$7 St!$ "'<9$vϠ04G` v4"!;]}$Ƣ%(Nds M)AWi+Ϥ%;+[$"%8^|8"Ҧ ##7G>&ݧ/4d'Ҩ -K&\ [C+E<q##Ҫ"-6G~!59<"(_4άG6LVAڭ j=WVW_"VWsO˱_{28E9~[*1? q}!="AIe0=ȶ"%H`.3)/ %=c !ڸ5*24]'$s߹2S6Oƺ#":"](-<׻(#=a{5ؼ*"C"f#)4׽) 6JY'a(˾I++WW!ѿ ,-E&s0I"b**%!6$X}#." "/#R$v1 0)0$Z  #) 9E?^*!&0 C d:-4(L u!-("Fi2#)"-L!z!5&,HP0jHC&(EO#2" #9]y )0%/63f " #&%F%l8"  :&Ip&4*&/On(  &Dbx Ffax##+O'f#8A!P#r#') )&I$p(&7+9-e 1M;:!v '"f?!?,05!f%wwB '0 ':2b .-&4[ v)+>j } - "?Wtd:"%]848!*+Lx:'%/,\x1%80F_=~)($:#T*x1  1LU"$8Wr#*/) $6$[e* &2Ym$ $@Tg.}0 $B,$o7(; %E!k(*,<?i* )82S15% *3"^&#5%P v' )B&\ /M*Al-/--"I-l$'5&\y+$&#F"j51:,g%y,+'%)M$w +0,7-d'1+'*"Ru+".&)2P&(##+Oo+?%17i !%;%a& #73,!`# <");5e$"$2%W$}$; JXow!%!=E<;%&"Ig#-')>++j$" / P!n+ ,,/\o8_%Ag-X$ 3T+p >%5Aw/>3"1)T,~N6 $Q v   0  * : "Y !|    w .V "  ( > + G  b 8o / 1 0 +; )g    / +IZj8L X)t)$@?.n%&5 Vr-)IE4e%6CTZ&##+Ol (!)AkI"6Ys",K?2!  2E\*z!')5-Rc6,[,&,!!KC'.H_)s-CUk{+EYo  % -< j / F @ $9!0^!!!!!!"3"S""m"#"!""""#*#L3#0#0## #$7$J$3c$6$.$#$3!%U%h%q%%%% %%&"&5&U&$m&&&&E&. '=O'+'+'5'.(@J(+(B(-('(),P)3})1)5)8*1R*1*P*+6'+5^++#+2+,,0,P,:n,",&,#,-'-8D-$}--;--& .4./L.)|."..#.//&6/,]/)/#/!/)/$0 C0M0S0 d0n00?00013514i1@141325H2&~242&2"3 $3p1333!353(4BG4"4"40485#:5?^5A5!516*46&_6(6;6-6\75v7a7A8?P8858!8(94-96b939099g:w{:#:";2:;2m;H;R;'<<d<rL=e=N%>@t>+>R>C4?Gx?'?*?'@(;@+d@3@@5@&A(9A3bAA/AAA'B,BHBCCuDE"EMFMGehGeG4HHkDIkIFJFcJJ+JJ Ky)KDKK+LMMh NuNN&NNNNO*.OYOxOOOOOOP<PNPGiP1P9P"Q@@Q5Q]QURkR+pR-R:R4S:SVS8SET_T{TTT;T0U(CU/lU,U:U-V'2V+ZVVW2W4W)"X.LX${X/XX#X Y-$Y.RY9Y>Y)YG$Z2lZZ-Z0Z[+6[!b[[[[3[,[,\.H\%w\$\#\F\-]*A]l]]9]],o^+^_+]`B``a4=barcYcW.e/fgi=kDmKqq\rpr6Rs.ssOt`tHuYurSvvqtwwkhxqx~Fyyzr{D{{b`||KU}}P!~Jr~l~u*_4qNxiǂ]16uƃ<|Z\n`RIPd<L~"0sf(qq,OUKIl_)yKӡm0*[@q*uݧ]S|f chV!x&=)bg ʸغDl5J<23oEL6E4Q(5^ |!~:^DS,2_,fv(t0P2 mDx;jBR7ztH[E:oD..@~ot"5}x74[CQ84#'  h   ^ P N4  )n,}L%yJ1 !#p%_'^J*/*r*L-)L/Gv13]J5'68q:<=S>;@-=AkAlEWE FFSGgH+JyK*LH NxSQkQ<8RMuTdU(V#W~X-Z[i[^\ %]0^^r_R_K_S"`Bv`B`A`K>ataiaBibub;"cY^cc cdf[hhij7@lxlWnuOopqKrgt uu[w9w*zz{|p2}~Vq~p$C=C2SvLʊ/Gڎ=Q@i` _=S^[k!eR}69ϟ[t?fYjgZg͵5jͺ8~{?MTj$R9 D 7CRCfS%yIoCIpL,t76]7d9vO  > tD Y 3 G oD Z |  I  &n = t gH W l u  M | g e Y  py f KQ o  h s1  B w Wh o 80 =i = T : [  h i ]Z ^ W o B> L! b! V! -M" f{" 6" # $ $Q% .v& ' ( ) * f@+ `+ - ]/ J1 B;2 >~3 5 6 B7 8 ,9 ; ~< ;> W> 4B *D E _ G lI QaL M N GQ U U W Z Z[ 6\ ] ] u^ _ ` G` ['a ba a 4b Jc =0g ng Oh !i 'j 6k ?l 7o 0q }5r kt u w Wy hz /i{ | u} (  O PA Uh  VƆ  I , 0 I Ў "I 6l   mW Ř  f O5 K b,  @ ߡ { ]   "4 HW d  1 B+ n w  J޶ ) u޷ :T : ʺ [ & ؽ i N ZQ  +  h  M  x N l $   w   5 : " R Y  l z  v `  +( T   _ P! r B !  s[ k p; } *   } P   L 5  } , k : KY   [ H 0 *  | ! -%# S# 3]$ % s& ) 70) >h) ) (* j* e+ 3, 1, .- 86- mo- .- . . ;/ 3 3 5 {6 <6 w6 87 0@9 2q9 09 J9 = : 9^: : ': ,:  ; :!; 9\; ; 1; ; < D= `_= = @ %C (C GC VE >kE =E FE //F :_F <F 2F 0 G h;G 4G HG ="H C`H 3H ;H !K 6N n'P Q 'IS WqT @T ' W ;2X nY mZ [ [ - ] 9^ =L^ ^ `` o` Ha cRb qb (c c 6id Ge Pe 9f f bg Xh uh i i j -k ak Sl dl Bm n U~o Do lp p p ٟ B [ *z  xà I< a    > [ȧ 3$ -X ^? s '  - ,> ,k E R ֯ r 6  = vK _µ " t o" q ` {q  \  P T Qb   U O/    "   ( (> g %y  / S D<  O pt r T Z Oz ,  5 c4 D     ; J  U U D "6 Y /  * . == `{ J <' Hd  S ] g q     ! + 3 ? F S Si  E 7 4O   9 b TM 0  & = 8T F E $ ? S  &  < P b .    9 65 l w 6 e @ )C km r FL B & @ (> *g V H K2 C~  : 1 NN 3 . - 5. 0d 3 m 7 #L p ) /6 Cf 5 P L1 M~ , B O< > 9 9 ? ,[ Q I )$ N Ak  O  , 8 > 1S > ! $  h& ' o ' H X^   & /5 'e o a 3_  H 4 S0 . . / C 5V A ; Y +d & * # W K^ L J XB X = 42 Cg ) $ -  41 6f S N -@ Gn C D 1? \q   1 N *h N 9j q 6 LM V O A Ab " % = u+ Q s [g 7 @ !< $^ N Z 3- ia  f 0@ uq W O?  ]   *L _w O O' sw ) O ze  J a MQ R  N , d@ n r S  sa } S kL x M1 B d d' ^" # % b' A( ) ) ) * "* + ,1+ H^+ B+ ,+ ', T?, &, , , &, %- 1>- 8p- g- . . ]!/ ./ d/ j0 K~0 L0 S1 5k1 91 l1 PH2 J2 (2 L 3 PZ3 73 3 3 44 JE4 4 4 4 4 E4 b$5 5 (5 U5 %6 $F6 [k6 r7 :8 9 : ; y< > ? `B C E F F PG H H 8I J K fL [M \M N xO |O |P d^Q Q T c_U U QWV oV X X Y wZ h[ L\ s\ ^] ^ o^ q6_ _ pS` p` m5a a b c 8d kFe e rf u g Yg g lh h i *j k 9l m Un p Fp Xq Zq ss iu u v 8w x M=z kz z | b} } x uz _ P ݀ wā <  J X l 1 i5 s H J   0 Ñ h   - s ~  u ) iZ WĤ  _  w V Mu é 7 ,Ь A ? ~ D Դ _ mq 4߷ 7 6L V ڸ : .1 "`   =E s U M L j c L I  L _ <  | p ( 7 @D  h   =   |U J  i DG r D AD  _ N MD # k " Y L [  -2 $`  :  Bz  q`     ] o  ? (   G , 7 jH p r$ 0 w @ ~S  b Fw V Z p ' '6 ^ l 9    " G3 { a   8 #  #  =1 o x  $ 3   u   uA  * _ %" R$ *b$ % y& ' b)' ( 1) Q) e`) M) + 2+ /E+ u+ u, >, . K/ g/ / / / ,/ / 0 20 uS0 0 2 4 7 M8 ^; :s< > l? A A xaC zC 6UD D D bG YH ABI mI I J ?J 8J K HL N krO GR &V V VX wY TZ H[ SO[ ] L^ / _ :a Jb e:c Hd f pg fi j k Ul l yl um 1en o 9Dp K~q ks 6u Su ,$ ak% ]& D+' p* =.+ (l. / b)0 1 4 4 +5 D6 -7 $8 z8 vV: ; = > ? fA C E *E , F 6F CG 8cG #G jG 7+H cI ^pJ KK L M YQ R S dT T W cW QX -YY Y H[ ] 5_ b [c ][d Vd Le ]e C%f tif 6h j j l n o )lp q r ns , t 2:t mt Ou >jv x [y gw{ { N| } 4  Ł S e 0 (   ۍ  2 Z@ g _ c !   gY & 9 D % D Π p * ǣ Z ;  T Uժ +  ߭  RЮ # 4   p Ak P   s 6  \Ժ 1 C nb hѾ +: f  k  I q ? [ A M e I ] #4 RX ?  z "   T   5 R ,r  - 3 ; C d u  [ I [K 1 9 / C W Ia &    B c $ 6  V F W .h  7 #  M *` ! ! 0 1 >2 Fq 5 ) , 4E z # ' 4 % B U ` q I 9^ @ [ j5 ) o D: B B  q %y  H { Qk B  R 2   Io|]5R0 NH]H,bXG.~fiNsP#in$L$%%7(J(*+- .E/L1t]1{1#N2r2 ?3vM44&i7<~$=> r] d 5  ^  f7gTTmAMdny4X"vRHV5@_<4HqDITIH#[8IWDZT_TT_ 1)@[AP\/_/t/YE.nts_WWz | f!hn!j!.B"q";"V""#3B#4v#&#>#o$ $[$W$ V%aw%#%D%,B&bo&q&CD'('A'X'4L([(5(\):p) )-))F):@*({*d*f +1p+"+I+,0.CA.`.e.LL/6/\/-0CL0Z001r&11O25m2f2I 3T303"%4#H4~l44j56!96"[6~6 66$656G 7KQ7E7g7AK8c88.s9k9H:*W: :/:":#:t;T;#;/<)8<&b<Y<I<@-='n===!=k=oT>>>>4?0F?%w?v?B@BW@%@1@:@-A-A}*BB_CvDI\J!KKOMQMeONSb[UU~VNW X?X_Y+Zv@Z/Z>Z&[):[Hd[?[[Q \[\H\v+]A]F]^+^^V _?c_$_m_S6`k``KaLaUbPtb;bRcGTcrcRdybdQdC.eHre@e\eNYfGf<fW-gegggJShWh6hb-iii^iXYj<jyjWikFk[lJdl\lF mCSm=mRmO(n|xnNnrDojoU"pOxp4pXpbVqKq~rWr\rP9s^s,st]tIuAOupuv/vvtKwOw/x[@xIx6x[y?yy[y9zPOzVzMz/E{6u{5{W{R:|U|J|R.}P}M}Q ~Er~P~F QPHXPD=Ӏ?Y<ZցR1JGςo97Q037dLfVPDƆ8 ,DZq̇V5=<sNLLLb^Ɋ)([R5Hh-MA57*m3K̍,ECd&iώ&90`*8F <.I5x3;y7lA?`9=ڒ/UHK.C==hy(rhi~ygbxʗiCZee$groSoÛ=ۛ-!Gi<;œ$&#J71$V;:SA$ПEL;H|Ѡ^N]V bb Ţ'ҢFA+`"/ߣ T,sm0!?a<jS(J|PǦF!_[Tݧ+2V^KB*DAoEn}K[8"SC rOX¬Q-m(0ĭ'-3'?[)tů_:ri w2M75F=| ۲__RgTRoG´ q2,=_K/0IJ0<ŹVKY- ӺLvT@˻> )K9u(JؼH#.l HnwbDI$j¿C-qE*J,u~e!\-Q=dUl5eJ2\1c1Z$6[=[P}B*(mB>o<XLKkhK4K.&H"$k=R9!r[1BQC2HOLa:'J;\)Vc~5ad0{?-Y?t,&,"8O0*24cL:8VGG_2cN>E1h*',C4^"B6g0=0[[cv-6dfn:V6C, :9_t1').gX0J0<Im&&H?I)rVo0=U50I8 3D(x9) !9BD|0p#c^daK` *9 2>JVN8[)(0?GmCO96T=SSI,~/]1P: ]EU*"*/M#}6)fiYx25DO,LM*(x0;;!X z (+OSa-?#*5E`O,-|q)/ Y!d0*BE%7k1!189.rSI/[./1.2K ~;. ,(U<q'EG2 zA / :7QK A0U "--#1>pDx^$;AP}9*$;/`41 / ; %[  G E S/ { c Ec<Ve=oJ5^89Z0b6+.QD9MG0fii:ka+!:M0t4L}L[LA-kbmUasMB#fcPK/G CCc/coUAY-5PnP"aXD A 6 >!fU!\!F"F`"5"<"A#F\#Q#=#T3$b$M$9%J%6]%#%<%K%<A&-~&%&J&J'(h'%'A'@'k:(2(.(>)%G).m)C)T)D5*=z*[*>+pS+#+d+[M,=,,9,9&-C`-&-^-#*.7N.#...Y.3/j/tY0{0_J1M11P5-5?!6Ja686F6,7K7=j7A77_ 8Gj8Y8 9>,9Uk9?9c::e:4:8:;I);Ns;7;M;SH<L<Q<2;=Cn=&=H=J">Em>4>>O?@4@n@O@AKA0AV BdB_BUXC2C.C%Dl6DGD0D,EIEIFWGEvG}G/:H/jH?H.HK IUIsIiI1I="Jc`J3J5Jf.KBKDKLLB?M MZMEM-0Nk^NN>Nq&OrO7 P.CPOrPIP QQ'>QfQQ_ R&jR'RYR\SpScSD[T(T\TJ&UqU>U1U$VH&V[oVkV"7WDZWZW+W`&XX(X@X)Y+YYB;ZC~ZAZ9[>[>[[3[8[\z\`]Hf]G]']8^1X^~^ _Y_D_#B`Hf`)`'`FaIHa2aEa7 b(Cblb<b.0c:_c'cvc9d5d.d@'e)heLeHe((fLQf6f2f.g17gjigKg# hCDh?h1hIh(Di0miii*>j*ijjOj(j$k%Bk(hk)k<k.kN'l)vl(l<l1mF8m,m5mBm %nCFnCnln:;o/vofo> p3Lp5pXpq^qCqS6r1r=r]r;XsZs)st9tQt*it.t&t>t,)uXVu'uuuvE w_fwAwBxEKx_xqxcy=yrym1zwz\{t{V{*{|*-|qX|y|D}}8~~Zm1K}̅DLnyhQRNd0ʌLrHKv1~O.m/uOIc08ސMueYۑr5`A :K87ߓ<^TIpDnAbObv6VS<KW3h1G&HnHD1EgwIߛ@)Yj_ĜK$lprݝcPҞePd3,vՠLA75y)%&h5P %NFAWפ)/@Y2-ͥuL1F>xF4]3!1KG1XyIҩSpF>BUYGG:J&ͬ<1G7~QMЮaVlׯADCʰ_Ѱ;1@m;<O'Hw(Q;;^wLֳZ#^~#ݴM4O_7VTs;ȶ@XEWN.E/taP'|xIc?5ٻ#L<h0ּAN2YY۽o5uZSv/ʿ2E-Ns>BD>C6;zZ01<btLLaA@_Q /H(q>31?e,/+.HHd02mV'ARX2_'>QfGe?>J^I\248^mgV4a3q!ddF] s"sWL#-NeER`_WSh-l4C8O|9 9ZXM;-mW0D #Rv%C->E#:M1,agT7DB|1)-17_$8o|O^<^bA]P1r"N@SA1&a Vnw4=Br@wgna8V,tW^dXU 94fn]M253(A`UWK>Z;Pc?P"E&h$,0$772oUE4M&S9,UEH:%Z`W0?A3GP{UV"HyH v>C^^|<Ca`JVe;hDT@>/N_: D5 >?&~O/+%)Q7{'M-)SW]c m=59Zo\' 8  J :k 6 d B O Q Qe _ Y nq Q E2 <x ' 2 nt,B@dT\CYZK$!%G(cS`oAhjn:l/Dj3LkcOP|_j}eSN=b<CKB?hOw]0AaB2HuAC=D=;3P0a6E ` ez ^ `?!^!C!IC"9""W"2;#?n#Y#($W1$K$W$Z-%K%m%XB&!&@&A&&@'og'#'M'I(0Z(I(E(=)tY))mZ*#*G*A4+3v+9+9+Q,Kp,4,[,hM-T- .v.:.=.B/I/`b/>/T0KW0,000X1[1sp101[22q2Y22_384I?44P:5#5U5;6FA676_6- 7N7QT7n798\O8h8[9>q9Y9_ :j:< ;bF;>;!;0 <F;<<2=]7=O=C=R)>|>>->>W?3?@*s@F@@9eA0A)A~AjyBNB3CMCZD)\D:D8DhD<cEZEEF71F iF[F2F=GWG9GgHEH@Hq IV{I IWI*KJ<vJFJ<JF7KA~K!K5KOL6hL~L.MQMMXMMD{NcN$OW5QXQ?Q=&RVdR\RhShS>S+)TAUT'T2TLTQ?U!U=UDU6V-V+V^%WAWOWaX]xXNX,%YERYxY9ZuKZIZJ [)V[+[3[A[J"\5m\T\T\VM]].^1^p!_p_`I`!a?9aIya:a5at4bMb(b' c/Hcxc.c,c/c1d&Kd8rd9dLd(2e-[e7e7e.e&(f*Of#zf&f$fCf'.gZVgZg& h*3h2^h7h:h8i9=i0wi#iBij7'jR_jaj(ke=khk^ lZklTl3m7Om3m5mLm1>n9pn2n7nAoIWoFoFo'/pWpvpwqqq*rG,r=trr(rrss]s]Ttft'uAuJVu)u:u&v=-v5kv v v?v-#w@Qw*w1w,wXxJuxxj[y[yl"z`zizgZ{{Ba|A|A|w(}S}L}A~H~UXL@"GPkITR ]Sj;X222er1atX8aJxH^sVr.G?\}]bLd rra+GsOÍPd9EJePdsfڐq_<ёbNqP!3BOVqIbCC,rpkFOyj:{]EFZUoxm }5VQKbkWkßk/X.#ǡ4OZV FgW;P)zy%;KXWG8QYҬ ,nManQ ߮FL36S) 5tP6q P [  nzh   #N J e >  ' MH \<N f a&= .2" x} p loA +& m g`S  .}} 5} T f) 3 . bu & + i :  mNm mi  ow %  * 2] , u  .%r0$  )r x 5{3`4f&Sw $v .{W`Op M  .  h~ 7 Z ^ Z-@ U { Xg 0o9k o  ;j 9T ?  ^Rk{   Ek-{n l)1 LP N z 4Bj pgF d ^(  9  tN#: cJ  :) y[ Z 2n | ?   h J  R 5 ZF6 ) B zX h  D e~  ( C 6U~  n6  V1Ge c_ f *m 5 I C -?u  U <s F    ; v$   6 ' " m q+ $ BIg  t4[ + "U6  L d JZ ,]8 -N [P V dY=Wer ' K -F G   o * R'  i f \&@  ]  N b W O P4 5~ Z ! H Zv !RSz kP: 9' m>  T<Us ]  4= 6/e ` \ z 7# 0  @ z h y 5 v g )O{ '   V:\ 7L@MX  { l0 I x L [[t & K - i s 1y: 3J 9  &j yE {  3kA Sw} |  @ 3z; j S   E ]T hP Uf$ i BW 1 JS| Q A d _ ` 7} '?   i] g 1  )B Z - x/ .Wd   V/ {r T; TX T n ) _ x SVa xc# UR m   y!( #  @I   b e 6sn*j M~ ^z7W > 4 \  Eba z 8 *VeD T %_ d j m M.    9K7  HkX - rs a"  w^ )wL k x @ a   O Sf Ta 6u$QE <?| a 3s L Pc !i yAsc tR S q 5  z X "  p  {    l E3+ [1 N $$ ^t  # s  - B>J9w < Qcr   F X"'W| D#c3 \:W    I   K b }hlrX  l1h 47vd s +s\" xR; 0 wg mK  v d 9? t Gt K(E Q- iJ Ow  A ]]QL 7 CbP z IC ) :n Qx  [ 1  ah ; < 9 D i snq MVK_  \=   ? c [   M ;  x v lZ 1 # hj y p    V s v a o#( RH "; G [q2 dS  O! a ( Zt 5I2 {Pqr 2 >v Uo D   8 Tq k$H m   ! I ' P  ?4+('e*t* IOh~ I + ^68 S <R%/ "l  $7 Y   q uU ! w8 C@j/0u ^ 1 =4Y`t] ]_9    + 2 o (Sl \u LiP } s F 67@K  Bk x Cl\Nb9  g   7C_r&)  ?z 0 G% 8 B   +  <w|NAA  A ^Y e f 0 ? n 'E Y  9 w X/  %  } i  ,  |v L o B= N  0 R Cv %#< f \ 8p  L2 1 %m  Mn^ e} XY t  K A F~ 5Gp:k O /( = o  Yx D U  M zC7 ,{3/ _j q K]  ] =e + 6 1  ! H5 |gNy*Ia 2  D ;    { k *D A8 hUQ}m [ \H :w1?P  X>y BE%O   ~HT   y ^ 2f'gv;]w)aCe >/ # T uMe  | yc O ~Ti:  tM | bJ `m cu zyK  m  uZ  B %q  ,>    8 7,w  M# * M'`~bAN !  6   .fG U W vng Np H {q${U$ L , : V Qr p GQD8% d @V +j Fb`h| dt'o 3Y 8    -B L nR "Z    ~+U G R~#W br 5\ A u Q  &  b a" ) @ oqPa R H >K # A e|Q  5'`G p&  y  #(;: K< / 7 ;%J< "/o D  - ^ pk bF 4 - c zY&E$;O&   = C = Fl ` 8b   3?* B -g O _ Rio F 06 HU$I i iw qM3  v <! V 6 &? ! # nX3/z0 ql=> Au4 B  rD IQ MI CP &I  JW g^ ?@! xWa 4 . * R XC1 YrX| * l ]B Y* NQ & A  f . A Vi{5<M ( Y ( - ,2  'k ' f Y     j   5 dE ( c H hO > |L  b: (  j=s E O@ ,_ O =  "w =+ -f 8 0  %J  n +SF. y" 9 A  ^  M;j _ DI u: 0;6 C  Hh[a ` ~_e@# : } '0 s p/  / aF. B a!Zj,2 c5`o9  _Z  ! ; > E C1g    Vl   x@ X $*)"t W( d-*% m |U> .   e( ;  0`=k5.  >:$  =\  FG ; ", y r8n% 1 k T 2 ]fdD X X 2  18s D ( l3 y ~  /Go Wv1eI  c rW   4g l   TPY%(2xS F H 5 t "  F,7 HY$  _ #I < - 4  f+U r9 _ N+ xS x B,* un N` & b 0P K <L L[jV r ,  !u t s D#] t pe . V G n  _ :1E OO  B  R KK /0 T  5!C"  EQW  d uY c jNV2 p p P> ?@0 m  q 6g |  {Q{  ^]   2i3.+ T  7+ ts[ xbo d8j6 lJ = Z } F g[yL/< @ D   ? ZDJJEF2q 8 ~M X  h K |CwL ^ G ? , 4S~ }  V<  * $p) Z  k J,G } }fGd .Q O 4: Cc!, %W7u"\ )l;p W4n^zg0^< J&9v%R3 !'  9r \ |6/h[y d )_Gk~ vqi ,`  ) @ 7=U4wJ}m4 . 7  3  o)  v ~ & u` 5 Yzj S c $K  *H%,> 8Z/\ 32>VL Yc Q  pk < & TS ! ?  [ ( 8  -Q   ]D_ 9`fE>[hE=  HRq A\9 b }G 3H 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 Adding a Subrepository ====================== Description =========== Enabled extensions: Examples ======== Final summary: Synopsis """""""" **hg** *command* [*option*]... [*argument*]... The following predicates are supported: 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`` -------- ``committemplate`` ------------------ ``defaults`` ------------ ``diff`` -------- ``extensions`` -------------- ``format`` ---------- ``hostfingerprints`` -------------------- ``http_proxy`` -------------- ``patch`` --------- ``paths`` --------- ``phases`` ---------- ``profiling`` ------------- ``subpaths`` ------------ ``ui`` ------ ``web`` ------- additional help topics: aliases: %s auction for merging merge bids broken pipe calculating bids for ancestor %s diffs (%d lines): diffs (truncated from %d to %d lines): keywords written to %s: use "hg help %s" to show the full help text use "hg help -c %s" to see help for the %s command hg archive -r 1.0 project-1.0.zip hg archive project.tar.gz -X ".hg*" 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 -r .^ tested hg book new-feature hg clone --uncompressed http://server/repo -u 1.5 hg clone -r 04e544 experimental/ good/ hg clone http://selenic.com/hg hg clone http://selenic.com/hg#stable hg clone project/ project-feature/ hg clone ssh://user@server//home/projects/alpha/ 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 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 http://selenic.com/hg/ hg import --exact proposed-fix.patch hg import -s 80 http://example.com/bugfix.patch hg import http://www.selenic.com/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 -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 -v hg status --copies --change 9353 hg status --rev 9353 hg status -an0 hg update stable hg graft --edit 9393 $ ls foo.c $ hg status ? foo.c $ hg add adding foo.c $ hg status A foo.c $ cp -al REPO REPOCLONE -----BEGIN CERTIFICATE----- ... (certificate in base64 PEM encoding) ... -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- ... (certificate in base64 PEM encoding) ... -----END CERTIFICATE----- hg transplant --branch REV --all public < draft < secret qguard foo.patch -- -stable (negative guard) qguard bar.patch +stable (positive guard) qselect stable An example showing how new (unknown) files are added automatically by :hg:`add`:: 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. Specifying negative guards now requires '--'. To check out earlier revisions, you should use :hg:`update REV`. To cancel an uncommitted merge (and lose your changes), use :hg:`update --clean .`. 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. export may generate unexpected diff output for merge changesets, as it will compare the merge changeset against its first parent only. for performance reasons, 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. log -p/--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:. 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. 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) - 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:: - attempt to exactly restore an exported changeset (not always possible):: - briefly list changes inside a bundle:: - changesets ancestral to the working directory:: - changesets showing all modifications of a file, including removals:: - 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):: - commit - import - pull - push (with this repository as the destination) - unbundle - 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 high-speed clone over a LAN 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 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:: - last 10 commits on the current branch:: - 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 the '@' bookmark from another branch:: - pull largefiles for all branch heads:: - pull largefiles on the default branch:: - 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 incoming changes excluding merges, store a bundle:: - show incoming changes with patches and full description:: - show the source of a grafted changeset:: - skip all revisions that do not touch directories ``foo`` or ``bar``:: - split outgoing changes into a series of patches with descriptive names:: - start a bisection with known bad revision 34, and good revision 12:: - summary of all changesets after the last tag:: - use 'make && make tests' to automatically find the first broken revision:: - 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. If neither -c/--check nor -C/--clean 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. With the -c/--check option, the update is aborted and the uncommitted changes are preserved. 3. With the -C/--clean option, uncommitted changes are discarded and the working directory is updated to the requested changeset. = ========= == == == == 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: 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 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: In some cases, you can clone repositories and the working directory using full hardlinks with :: 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: Note that remove never deletes files in Added [A] state from the working directory, not even if option --force is specified. See :hg:`help revsets` for more about the `bisect()` keyword. Some examples: The -c/--continue option does not reapply earlier options. The ``.hgsubstate`` file should not be edited manually. The following rules apply when the working directory contains uncommitted changes: 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): This is the fastest way to clone, but it is not always safe. The operation is not atomic (making sure REPO is not modified during the operation is up to you) and you have to make sure your editor breaks hardlinks (Emacs and most Linux Kernel tools do so). Also, this is not compatible with certain extensions that place their metadata under the .hg directory, such as mq. 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. 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 backout cannot be used to fix either an unwanted or incorrect merge. d - done, skip remaining changes and files a - record all changes to all remaining files q - quit, recording no changes exclude path/to/file-or-dir hg email -b # send bundle of all patches not in default hg email -b DEST # send bundle of all patches not in DEST hg email -b -r 3000 # bundle of all ancestors of 3000 not in default hg email -b -r 3000 DEST # bundle of all ancestors of 3000 not in DEST hg email -o # send all patches not in default hg email -o DEST # send all patches not in DEST hg email -o -r 3000 # send all ancestors of 3000 not in default hg email -o -r 3000 DEST # send all ancestors of 3000 not in DEST hg email -o -m mbox && # generate an mbox file... mutt -R -f mbox # ... and view it with mutt hg email -o -m mbox && # generate an mbox file ... formail -s sendmail \ # ... and use formail to send from the mbox -bm -t < mbox # ... using sendmail hg email -r 3000 # send patch 3000 only hg email -r 3000 -r 3001 # send patches 3000 and 3001 hg email -r 3000:3005 # send patches 3000 through 3005 hg email 3000 # send patch 3000 (deprecated) hg qguard other.patch -- +2.6.17 -stable hg qimport -e existing-patch -n new-name include path/to/file-or-dir key parent1, parent2 original_branch_name new_branch_name rename path/to/source path/to/destination s - skip remaining changes to this file f - record remaining changes to this file source author = destination author y - record this change n - skip this change e - edit this change manually - "+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 - "= .5MB (files at least 524288 bytes) - 4k - 1MB (files from 4096 bytes to 1048576 bytes) - :hg:`resolve -l`: list files which had or still have conflicts. In the printed list, ``U`` = unresolved and ``R`` = resolved. - :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`) - Unknown files: files marked with "?" by :hg:`status` - Empty directories: in fact Mercurial ignores directories unless they contain files under source control management - ``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 - if it's a directory, all files ending with .rc are added - otherwise, the file itself will be added - transplant all changes up to REV on top of your current revision:: --branchsort convert from parent to child revision when possible, which means branches are usually converted one after the other. It generates more compact repositories. --closesort try to move closed revisions as close as possible to parent branches, only supported by Mercurial sources. --datesort sort revisions by date. Converted repositories have good-looking changelogs but are often an order of magnitude larger than the same ones generated by --branchsort. --source/-s specifies another repository to use for selecting changesets, just as if it temporarily had been pulled. If --branch/-b is specified, these revisions will be used as heads when deciding which changesets to transplant, just as if only these revisions had been pulled. If --all/-a is specified, all the revisions up to the heads specified with --branch will be transplanted. --sourcesort try to preserve source revisions order, only supported by Mercurial sources. -e/--edit, -m/--message or -l/--logfile set the patch header as well as the commit message. If none is specified, the header is empty and the commit message is '[mq]: PATCH'. -u/--user and -d/--date can be used to set the (given) user and date, respectively. -U/--currentuser and -D/--currentdate set user to current user and date to current date. 1. ``us-ascii``: always first, regardless of settings 2. ``email.charsets``: in order given by user 3. ``ui.fallbackencoding``: if not in email.charsets 4. ``$HGENCODING``: if not in email.charsets 5. ``utf-8``: always last, regardless of settings :``%%``: literal "%" character :``%H``: changeset hash (40 hexadecimal digits) :``%N``: number of patches being generated :``%R``: changeset revision number :``%b``: basename of the exporting repository :``%h``: short-form changeset hash (12 hexadecimal digits) :``%m``: first line of the commit message (only alphanumeric characters) :``%n``: zero-padded sequence number, starting at 1 :``%r``: zero-padded changeset revision number :``%%``: literal "%" character :``%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 :``files``: a directory full of files (default) :``tar``: tar archive, uncompressed :``tbz2``: tar archive, compressed using bzip2 :``tgz``: tar archive, compressed using gzip :``uzip``: zip archive, uncompressed :``zip``: zip archive, compressed using deflate :convert.cvsps.cache: Set to False to disable remote log caching, for testing and debugging purposes. Default is True. :convert.cvsps.fuzz: Specify the maximum time (in seconds) that is allowed between commits with identical user and log message in a single changeset. When very large files were checked in as part of a changeset then the default may not be long enough. The default is 60. :convert.cvsps.mergefrom: Specify a regular expression to which commit log messages are matched. If a match occurs, then the conversion process will add the most recent revision on the branch indicated in the regex as the second parent of the changeset. Default is ``{{mergefrombranch ([-\w]+)}}`` :convert.cvsps.mergeto: Specify a regular expression to which commit log messages are matched. If a match occurs, then the conversion process will insert a dummy revision merging the branch on which this log message occurs to the branch indicated in the regex. Default is ``{{mergetobranch ([-\w]+)}}`` :convert.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.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.startrev: specify initial Perforce revision (a Perforce changelist number). :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``. :hg:`resolve` must be used to resolve unresolved files. :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. = []... . = . = = >>> person('foo@bar') 'foo' >>> person('Foo Bar ') 'Foo Bar' >>> person('"Foo Bar" ') 'Foo Bar' >>> person('"Foo "buz" Bar" ') 'Foo "buz" Bar' >>> # The following are invalid, but do exist in real-life ... >>> person('Foo "buz" Bar ') 'Foo "buz" Bar' >>> person('"Foo Bar ') 'Foo Bar' 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 successors set of changeset A is a consistent group of revisions that succeed A. It contains non-obsolete changesets only. 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 running this command you will need to make sure that largefiles is enabled anywhere you intend to push the new repository. All string valued-elements are either strictly alphanumeric, or must be enclosed in double quotes ("..."), with "\" as escape character. 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 compressed changegroup files generated by the bundle command. Applying bundles preserves all changeset contents including permissions, copy/rename information, and revision history. As a shortcut, you can also use the revision argument to mark a revision as good or bad without checking it out first. Be careful with purge, as you could irreversibly delete some files you forgot to add to the repository. If you only want to print the list of files that this program would delete, use the --print option. Because import first applies changes to the working directory, import will abort if there are outstanding changes. Before using this command, you will need to enable email in your hgrc. See the [email] section in hgrc(5) for details. Bookmarks are labels on changesets to help track lines of development. Bookmarks are unversioned and can be moved, renamed and deleted. Deleting or moving a bookmark has no effect on the associated changesets. Bookmarks can be pushed and pulled between repositories (see :hg:`help push` and :hg:`help pull`). If a shared bookmark has diverged, a new 'divergent bookmark' of the form 'name@path' will be created. Using :hg:'merge' will resolve the divergence. Bookmarks can be renamed, copied and deleted. Bookmarks are local, unless they are explicitly pushed or pulled between repositories. Pushing and pulling bookmarks allow you to collaborate with others on a branch without creating a named branch. Branches may be created when changes are pulled from or pushed to a remote repository, since new heads may be created by these operations. Note that the term branch can also be used informally to describe a development process in which certain development is done independently of other development. This is sometimes done explicitly with a named branch, but it can also be done locally, using bookmarks or clones and anonymous branches. Bundle must be specified by the -R option. But it will leave untouched: By default the patch is included as text in the email body for easy reviewing. Using the -a/--attach option will instead create an attachment for the patch. With -i/--inline an inline attachment will be created. You can include a patch both as text in the email body and as a regular or an inline attachment by combining the -a/--attach or -i/--inline with the --body option. By default this command prints revision number and changeset id, tags, non-trivial parents, user, date and time, and a summary for each commit. When the -v/--verbose switch is used, the list of changed files and full commit message are shown. By default, abort if the working directory contains uncommitted changes. With --keep-changes, abort only if the uncommitted files overlap with patched files. With -f/--force, backup and discard changes made to such files. By default, abort if the working directory contains uncommitted changes. With --keep-changes, abort only if the uncommitted files overlap with patched files. With -f/--force, backup and patch over uncommitted changes. By default, all sources except Mercurial will use --branchsort. Mercurial uses --sourcesort to preserve original revision numbers order. Sort modes have the following effects: By default, 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 only prints output for the first revision of a 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 recreates the changesets in the source branch as descendants of dest and then destroys the originals. Use ``--keep`` to preserve the original source changesets. Some changesets in the source branch (e.g. merges from the destination branch) may be dropped if they no longer contribute any change. By default, the revision used is the parent of the working directory; use -r/--rev to specify a different revision. By default, the server logs accesses to stdout and errors to stderr. Use the -A/--accesslog and -E/--errorlog options to log to files. By default, this command copies the contents of files as they exist in the working directory. If invoked with -A/--after, the operation is recorded, but no copying is performed. By default, this command searches all directories in the working directory. To search just the current directory and its subdirectories, use "--include .". CVS Source ########## CVS source will use a sandbox (i.e. a checked-out copy) from CVS to indicate the starting point of what will be converted. Direct access to the repository files is not needed, unless of course the repository is ``:local:``. The conversion uses the top level directory in the sandbox to find the CVS repository, and then uses CVS rlog commands to find files to convert. This means that unless a filemap is given, all files under the starting directory will be converted, and that any directory reorganization in the CVS sandbox is ignored. Changeset 3b16791d6642 in repository-name. http://my-project.org/hg/repository-name/rev/3b16791d6642 Changeset commit comment. Bug 1234. Changesets that are ancestors of the current revision, that have already been grafted, or that are merges will be skipped. Closed heads can be re-opened by committing new changeset as the child of the changeset that marks a head as closed. Comment lines start with ``#``. A specified path matches if it equals the full relative name of a file or one of its parent directories. The ``include`` or ``exclude`` directive with the longest matching path applies, so line order does not matter. Commit changes to the given files into the repository. Unlike a centralized SCM, this operation is a local operation. See :hg:`push` for a way to actively distribute your changes. Completion extends only to the next path segment unless --full is specified, in which case entire paths are used. 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. Delete files not known to Mercurial. This is useful to test local and uncommitted changes in an otherwise-clean source tree. Differences between files are shown using the unified diff format. Do not attempt any read operations on this repository while the command is running. (Both repositories will be locked against writes.) Each member added to an archive file has a directory prefix prepended. Use -p/--prefix to specify a format string for the prefix. The default is the basename of the archive, with suffixes removed. Each patch email has a Subject line of "[PATCH M of N] ...", using the first line of the changeset description as the subject text. The message contains two or three parts. First, the changeset description. Each shelved change has a name that makes it easier to find later. The name of a shelved change defaults to being based on the active bookmark, or if there is no active bookmark, the current named branch. To specify a different name, use ``--name``. Elements: Empty lines and lines starting with a ``#`` are ignored. 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: 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:: 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 or descendants 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 a faster but less accurate result, consider using ``filelog()`` instead. For advanced usage, a third way is available through the ``--rev`` option. It allows you to specify an arbitrary set of changesets to rebase. Descendants of revs you specify with this option are not automatically included in the rebase. For each element in HGRCPATH: 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 remote repository, using --bundle avoids downloading the changesets twice if the incoming is followed by a pull. For safety, this command is aborted, also if there are ambiguous outgoing revisions which may confuse users: for example, there are multiple branches containing outgoing revisions. Generate a compressed changegroup file collecting changesets not known to be in another repository. Given a topic, extension, or command name, print help for that topic. Guards control whether a patch can be pushed. A patch with no guards is always pushed. A patch with a positive guard ("+foo") is pushed only if the :hg:`qselect` command has activated it. A patch with a negative guard ("-foo") is never pushed if the :hg:`qselect` command has activated it. Heads are where development generally takes place and are the usual targets for update and merge operations. Here 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 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 may happen due to character set problems or other deficiencies in the text patch format. If --log is specified, log messages will have a comment appended of the form:: If -B/--bookmark is used, the specified bookmarked revision, its ancestors, and the bookmark will be pushed to the remote repository. If -a/--active is specified, only show active branches. A branch is considered active if it contains repository heads. If -c/--closed is specified, also show branch heads marked closed (see :hg:`commit --close-branch`). If -e/--edit is specified, Mercurial will start your configured editor for you to enter a message. In case qrefresh fails, you will find a backup of your message in ``.hg/last-message.txt``. If -r/--rev is used, the specified revision and all its ancestors will be pushed to the remote repository. If -s/--short is specified, files currently included in the patch will be refreshed just like matched files and remain in the patch. If -t/--topo is specified, named branch mechanics will be ignored and only topological heads (changesets with no children) will be shown. If REV is the parent of the working directory, then this new changeset is committed automatically. Otherwise, hg needs to merge the changes and the merged result is left uncommitted. If SOURCE is omitted, the 'default' path will be used. See :hg:`help urls` for more information. If STARTREV is specified, only those heads that are descendants of STARTREV will be displayed. If ``REVMAP`` isn't given, it will be put in a default location (``/.hg/shamap`` by default). The ``REVMAP`` is a simple text file that maps each source commit ID to the destination ID for that revision, like so:: If `name` starts with `re:`, the remainder of the name is treated as a regular expression. To match a bookmark that actually starts with `re:`, use the prefix `literal:`. If `name` starts with `re:`, the remainder of the name is treated as a regular expression. To match a tag that actually starts with `re:`, use the prefix `literal:`. If `string` starts with `re:`, the remainder of the name is treated as a regular expression. To match a branch that actually starts with `re:`, use the prefix `literal:`. If `string` starts with `re:`, the remainder of the string is treated as a regular expression. To match a user that actually contains `re:`, use the prefix `literal:`. If `value` starts with `re:`, the remainder of the value is treated as a regular expression. To match a value 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 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 merge, it can be continued with --continue/-c or aborted with --abort/-a. If a shelved change is applied successfully, the bundle that contains the shelved changes is deleted afterwards. 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 directories are given on the command line, only files in these directories are considered. 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 merges or revisions are provided, :hg:`transplant` will start an interactive changeset browser. If no names are given, add all files to the repository. 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 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 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 changeset is not a descendant or ancestor of the working directory's parent, 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 pulled changes add a new branch head, the head is automatically merged, and the result of the merge is committed. Otherwise, the working directory is updated to include the new changes. If the source repository has a bookmark called '@' set, that revision will be checked out in the new repository by default. If 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 uses the current branch tip as the destination. (The 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 omit the destination repository, then hg assumes the destination will have all the nodes you specify with --base parameters. To create a bundle containing all changesets, use -a/--all (or --base null). 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 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). In case email sending fails, you will find a backup of your series introductory message in ``.hg/last-email.txt``. In its default configuration, Mercurial will prevent you from rebasing published changes. See :hg:`help phases` for details. In most cases a changeset A has a single successors set containing a single successor (changeset A replaced by A'). Initialize a new repository and working directory that shares its history with another repository. Initialize a new repository in the given directory. If the given directory does not exist, it will be created. It is not possible to amend public changesets (see :hg:`help phases`) or changesets that have children. It is possible to limit the amount of source history to be converted by specifying an initial Perforce revision: 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 an ``ssh://`` URL as the destination. See :hg:`help urls` for more information. List changes in files, showing the revision id responsible for each line List the repository's named branches, indicating which ones are inactive. If -c/--closed is specified, also list branches which have been marked closed (see :hg:`commit --close-branch`). List which files in the working directory are matched by the [keyword] configuration patterns. Mark dest as copies of sources; mark sources for deletion. If dest is a directory, copies are put in that directory. If dest is a file, there can only be one source. Mark dest as having copies of source files. If dest is a directory, copies are put in that directory. If dest is a file, the source must be a single file. Mark the specified files so they will no longer be tracked after the next commit. Mercurial Destination ##################### Mercurial Source ################ Merge changesets may be transplanted directly by specifying the proper parent changeset by calling :hg:`transplant --parent`. Merges with unresolved conflicts are often the result of non-interactive merging using the ``internal:merge`` configuration setting, or a command-line merge tool like ``diff3``. The resolve command is used to manage the files involved in a merge, after :hg:`merge` has been run, and before :hg:`commit` is run (i.e. the working directory must have two parents). See :hg:`help merge-tools` for information on configuring merge tools. Message, user and date are taken from the amended commit unless specified. When a message isn't specified on the command line, the editor will open with the message of the amended commit. Modified files are saved with a .orig suffix before reverting. To disable these backups, use --no-backup. 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. New files are ignored if they match any of the patterns in ``.hgignore``. As with add, these changes take effect at the next commit. Nodes printed as an @ character are parents of the working directory. Note that 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. 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. One result of the rules for selecting the destination changeset and source branch is that, unlike ``merge``, rebase will do nothing if you are at the branch tip of a named branch with two heads. You need to explicitly specify source and/or destination (or ``update`` to the other head, if it's the head of the intended source branch). 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 `bumped`. 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 may be to a file, in which case the name of the file is given using a format string. The formatting rules are as follows: Output may be to a file, in which case the name of the file is given using a format string. The formatting rules as follows: 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. Per-installation configuration files, searched for in the directory where Mercurial is installed. ```` is the parent directory of the **hg** executable (or symlink) being run. For example, if installed in ``/shared/tools/bin/hg``, Mercurial will look in ``/shared/tools/etc/mercurial/hgrc``. Options in these files apply to all Mercurial commands executed by any user in any directory. Per-installation/system configuration files, for the system on which Mercurial is running. Options in these files apply to all Mercurial commands executed by any user in any directory. Registry keys contain PATH-like strings, every part of which must reference a ``Mercurial.ini`` file or be a directory where ``*.rc`` files will be read. Mercurial checks each of these locations in the specified order until one or more configuration files are detected. Per-repository configuration options that only apply in a particular repository. This file is not version-controlled, and will not get transferred during a "clone" operation. Options in this file override options in all other configuration files. On Plan 9 and Unix, most of this file will be ignored if it doesn't belong to a trusted user or to a trusted group. See the documentation for the ``[trusted]`` section below for more details. Per-system configuration files, for the system on which Mercurial is running. Options in these files apply to all Mercurial commands executed by any user in any directory. Options in these files override per-installation options. Per-user configuration file(s), for the user running Mercurial. On Windows 9x, ``%HOME%`` is replaced by ``%APPDATA%``. Options in these files apply to all Mercurial commands executed by this user in any directory. Options in these files override per-system and per-installation options. 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 http://mercurial.selenic.com/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. Prepare a new changeset with the effect of REV undone in the current working directory. 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 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. 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. 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``. Results are displayed as follows:: Return 0 on success. Returns 0 if a match is found, 1 otherwise. Returns 0 if all files are successfully added. Returns 0 if import succeeded. Returns 0 if matching heads are found, 1 if not. Returns 0 if push was successful, 1 if nothing to push. Returns 0 if successful, 1 if nothing to recover or verify fails. Returns 0 if successful. Returns 0 if there are incoming changes, 1 otherwise. Returns 0 if there are outgoing changes, 1 otherwise. Returns 0 on success, 1 if NAME does not exist. Returns 0 on success, 1 if an update had unresolved files. Returns 0 on success, 1 if an update has unresolved files. Returns 0 on success, 1 if any files fail a resolve attempt. Returns 0 on success, 1 if any warnings encountered. Returns 0 on success, 1 if errors are encountered. Returns 0 on success, 1 if no changes found. Returns 0 on success, 1 if no phases were changed or some could not be changed. 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 there are unresolved files. Returns 0 on success, 1 if user intervention is required (not only for intentional "edit" command, but also for resolving unexpected conflicts). Returns 0 on success, 1 on partial success (see --partial). Returns 0 on success. Returns 0 on success. Returns 0 on successful completion. Returns 0 on successful creation of a new patch. Returns 0. Run after (re)enabling keyword expansion. Schedule files to be version controlled and added to the repository. Schedule the indicated files for removal from the current branch. Search revisions of files for a regular expression. 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 keyword` on how to construct patterns both for inclusion and exclusion of files. See :hg:`help qnew` & :hg:`help record` for more information and usage. See :hg:`help revisions` and :hg:`help revsets` for more about specifying revisions. See :hg:`help templates` for information on templates and filters. See :hg:`help templates` for more about pre-packaged styles and specifying custom templates. See :hg:`help urls` for details on specifying URLs. See :hg:`help urls` for more information. See pull for details of valid destination formats. See pull for valid source format details. Selected changesets will be applied on top of the current working directory with the log of the original changeset. The changesets are copied and will thus appear twice in the history with different identities. Setting HGPLAINEXCEPT to anything (even an empty string) will enable plain mode. Shelving takes files that "hg status" reports as not clean, saves the modifications to a bundle (a shelved change), and reverts the files so that their state in the working directory becomes clean. Show 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 %(path)s program. Show differences between revisions for the specified files. Show new changesets found in the specified path/URL or the default pull location. These are the changesets that would have been pulled if a pull at the time you issued this command. Show status of files in the repository. If names are given, only files that match are shown. Files that are clean or ignored or the source of a copy/move operation, are not listed unless -c/--clean, -i/--ignored, -C/--copies or -A/--all are given. Unless options described with "show only ..." are given, the options -mardu are used. Shows a diff which includes the current patch as well as any changes which have been made in the working directory since the last refresh (thus showing what the current patch would become after a qrefresh). Similarly, passing --rev to "hg clone" will fail to use any hardlinks, falling back to a complete copy of the source repository. Since tag names have priority over branch names during revision lookup, using an existing branch name as a tag name is discouraged. Since you can restore a shelved change on top of an arbitrary commit, it is possible that unshelving will result in a conflict between your changes and the commits you are unshelving onto. If this occurs, you must resolve the conflict, then use ``--continue`` to complete the unshelve operation. (The bundle will not be deleted until you successfully complete the unshelve.) Source history can be retrieved starting at a specific revision, instead of being integrally converted. Only single branch conversions are supported. Source patch repository is looked for in /.hg/patches by default. Use -p to change. Special fields are ``summary`` and ``metadata``: ``summary`` matches the first line of the description. ``metadata`` is equivalent to matching ``description user date`` (i.e. it matches the main metadata fields). Specifying a path to a repository root or Mercurial bundle will cause lookup to operate on that repository/bundle. Start a local HTTP repository browser and pull server. You can use this for ad-hoc sharing and browsing of repositories. It is recommended to use a real web server to serve a repository for longer periods of time. Statistics are based on the number of changed lines, or alternatively the number of matching revisions if the --changesets option is specified. Strip is not a history-rewriting operation and can be used on changesets in the public phase. But if the stripped changesets have been pushed to a remote repository you will likely pull them again. Subversion Source ################# Subversion source detects classical trunk/branches/tags layouts. By default, the supplied ``svn://repo/path/`` source URL is converted as a single branch. If ``svn://repo/path/trunk`` exists it replaces the default branch. If ``svn://repo/path/branches`` exists, its subdirectories are listed as possible branches. If ``svn://repo/path/tags`` exists, it is looked for tags referencing converted branches. Default ``trunk``, ``branches`` and ``tags`` values can be overridden with following options. Set them to paths relative to the source URL, or leave them blank to disable auto detection. Such a file may be specified with the --aliases option, otherwise a .hgchurn file will be looked for in the working directory root. Aliases will be split from the rightmost "=". Supports switching between different patch queues, as well as creating new patch queues and deleting existing ones. Tag commits are usually made at the head of a branch. If the parent of the working directory is not a branch head, :hg:`tag` aborts; use -f/--force to force the tag commit to be based on a non-head changeset. Tags are used to name particular revisions of the repository and are very useful to compare different revisions, to go back to significant earlier versions or to mark branch points as releases, etc. Changing an existing tag is normally disallowed; use -f/--force to override. The --amend flag can be used to amend the parent of the working directory with a new commit that contains the changes in the parent in addition to those currently reported by :hg:`status`, if there are any. The old commit is stored in a backup bundle in ``.hg/strip-backup`` (see :hg:`help bundle` and :hg:`help unbundle` on how to restore it). The --files and --dirs options can be used to direct purge to delete only files, only directories, or both. If neither option is given, both will be deleted. The Mercurial 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 ``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 archive type is automatically detected based on file extension (or override using -t/--type). 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 current working directory is updated with all changes made in the requested revision since the last common predecessor revision. 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 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 options are supported: The following options can be set with ``--config``: The following options can be used with ``--config``: The header for each folded patch will be concatenated with the current patch header, separated by a line of ``* * *``. The information shown in the changeset header is: author, date, branch name (if non-default), changeset hash, parent(s) and commit comment. The key is the revision ID in the source revision control system whose parents should be modified (same format as a key in .hg/shamap). The values are the revision IDs (in either the source or destination revision control system) that should be used as the new parents for that node. For example, if you have merged "release-1.0" into "trunk", then you should specify the revision on "trunk" as the first parent and the one on the "release-1.0" branch as the second. The keys can be: The location of the source is added to the new repository's ``.hg/hgrc`` file, as the default to be used for future pulls. The 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``. Note that ``default`` and ``default-push`` apply to all inbound (e.g. :hg:`incoming`) and outbound (e.g. :hg:`outgoing`, :hg:`email` and :hg:`bundle`) operations. 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 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). This activates the "stable" guard. mq will skip foo.patch (because it has a negative match) but push bar.patch (because it has a positive match). This can be especially useful if your changes have been applied to an upstream repository, or if you are about to push your changes to upstream. This command accepts an optional name of a shelved change to restore. If none is given, the most recent shelved change is used. This command behaves differently than Unix grep. It only accepts Python/Perl regexps. It searches repository history, not the working directory. It always prints the revision number in which a match appears. This command edits changesets between ANCESTOR and the parent of the working directory. This command helps to find changesets which introduce problems. To use, mark the earliest changeset you know exhibits the problem as bad, then mark the latest changeset which is free from the problem as good. Bisect will update your working directory to a revision for testing (unless the -U/--noupdate option is specified). Once you have performed tests, mark the working directory as good or bad, and bisect will either update to another candidate changeset or announce that it has found the bad revision. This command is deprecated, please use :hg:`heads` instead. This command is deprecated, use :hg:`rebase` instead. This command is deprecated. Without -c, it's implied by other relevant commands. With -c, use :hg:`init --mq` instead. This command is deprecated; use :hg:`commit --mq` instead. This command is intended as a debugging tool for the CVS to Mercurial converter, and can be used as a direct replacement for cvsps. This command is not available when committing a merge. This command is not intended for use on public repositories. Once changes are visible for pull by other users, rolling a transaction back locally is ineffective (someone else may already have pulled the changes). Furthermore, a race is possible with readers of the repository; for example an in-progress pull from the repository may fail if a rollback is performed. This command is useful for discovering when a change was made and by whom. This command lets you recreate those hardlinks and reclaim that wasted space. This command schedules the files to be removed at the next commit. To undo a remove before that, see :hg:`revert`. To undo added files, see :hg:`forget`. This command should be used with care. There is only one level of rollback, and there is no way to undo a rollback. It will also restore the dirstate at the time of the last transaction, losing any dirstate changes since that time. This command does not alter the working directory. This command supports shells that offer path name completion. It currently completes only files already known to the dirstate. This command takes effect at the next commit. To undo a rename before that, see :hg:`revert`. This command takes effect with the next commit. To undo a copy before that, see :hg:`revert`. This command tries to fix the repository status after an interrupted operation. It should only be necessary when Mercurial suggests it. This command uses Mercurial's merge logic to copy individual changes from other branches without merging branches in the history graph. This is sometimes known as 'backporting' or 'cherry-picking'. By default, graft will copy user, date, and description from the source changesets. This command will display a histogram representing the number of changed lines or revisions, grouped according to the given template. The default template will group changes by author. The --dateformat option may be used to group the results by date instead. This feature is only supported when using Python 2.6 or later. If you wish to use it with earlier versions of Python, install the backported version of the ssl library that is available from ``http://pypi.python.org``. This finds all changes from the repository at the specified path or URL and adds them to a local repository (the current one unless -R is specified). By default, this does not update the copy of the project in the working directory. This finds all changes from the repository at the specified path or URL and adds them to the local repository. This generates a brief summary of the working directory state, including parents, branch, commit status, and available updates. This is useful for writing repository conversion tools, but should be used with care. This lists both regular and local tags. When the -v/--verbose switch is used, a third column "local" is printed for local tags. This means that purge will delete the following by default: This only removes files from the current branch, not from the entire project history, and it does not delete them from the working directory. This operation is symmetrical to pull: it is identical to a pull in the destination repository from the current one. This predicate uses ``glob:`` as the default kind of pattern. This repository will be relinked to share space with ORIGIN, which must be on the same local disk. If ORIGIN is omitted, looks for "default-relink", then "default", in [paths]. This will perform an extensive check of the repository's integrity, validating the hashes and checksums of each entry in the changelog, manifest, and tracked files, as well as the integrity of their crosslinks and indices. To cancel an uncommitted merge (and lose your changes), use :hg:`update --clean .`. To check out a particular version, use -u/--update, or -U/--noupdate to create a clone with no working directory. To create a new queue, use -c/--create. The queue is automatically made active, except in the case where there are applied patches from the currently active queue in the repository. Then the queue will only be created and switching will fail. To delete an existing queue, use --delete. You cannot delete the currently active queue. To delete specific shelved changes, use ``--delete``. To delete all shelved changes, use ``--cleanup``. To disable SSL verification temporarily, specify ``--insecure`` from command line. To facilitate version control, distribution, and merging of tags, they are stored as a file named ".hgtags" which is managed similarly to other project files and can be hand-edited if necessary. This also means that tagging creates a new commit. The file ".hg/localtags" is used for local tags (not shared among repositories). To have the server choose a free port number to listen on, specify a port number of 0; in this case, the server will print the port number it uses. To import a patch from standard input, pass - as the patch file. When importing from standard input, a patch name must be specified using the --name flag. To import an existing patch while renaming it:: To match more than one field pass the list of fields to match separated by spaces (e.g. ``author description``). To pull only a subset of changesets, specify one or more revisions identifiers with -r/--rev or branches with -b/--branch. The resulting clone will contain only the specified changesets and their ancestors. These options (or 'clone src#rev dest') imply --pull, even for local source repositories. Note that specifying a tag will include the tagged changeset but not the changeset containing the tag. To read a patch from standard input, use "-" as the patch name. If a URL is specified, the patch will be downloaded from it. See :hg:`help dates` for a list of formats valid for -d/--date. To restore these changes to the working directory, using "hg unshelve"; this will work even if you switch to a different commit. To see a list of existing shelved changes, use the ``--list`` option. For each shelved change, this will print its name, age, and description; use ``--patch`` or ``--stat`` for more details. To select a different program, use the -p/--program option. The program will be passed the names of two directories to compare. To pass additional options to the program, use -o/--option. These will be passed before the names of the directories to compare. To set guards on another patch:: To stop managing a patch and move it into permanent history, use the :hg:`qfinish` command. To undo a forget before the next commit, see :hg:`add`. To undo an uncommitted merge, use :hg:`update --clean .` which will check out a clean copy of the original merge parent, losing all changes. Transactions are used to encapsulate the effects of all commands that create new changesets or propagate existing changesets into a repository. Unfortunately, subsequent pulls into either repository will break hardlinks for any files touched by the new changesets, even if both repositories end up pulling the same changes. Unless -f/--force is specified, :hg:`phase` won't move changeset from a lower phase to an higher phase. Phases are ordered as follows:: Unless -f/--force is specified, branch will not let you set a branch name that already exists, even if it's inactive. Update sets the working directory's parent revision to the specified changeset (see :hg:`help parents`). Update the repository's working directory to the specified changeset. If no changeset is specified, update to the tip of the current named branch and move the current bookmark (see :hg:`help bookmarks`). 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 --bypass to apply and commit patches directly to the repository, not touching the working directory. Without --exact, patches will be applied on top of the working directory parent revision. Use --new-branch if you want to allow push to create a new named branch that is not present at the destination. This allows you to only create a new branch without forcing other changes. Use --partial to ensure a changeset will be created from the patch even if some hunks fail to apply. Hunks that fail to apply will be written to a .rej file. Conflicts can then be resolved by hand before :hg:`commit --amend` is run to update the created changeset. This flag exists to let people import patches that partially apply without losing the associated metadata (author, date, description, ...). Note that when none of the hunk applies cleanly, :hg:`import --partial` will create an empty changeset, importing only the patch metadata. Use --to-normal to convert largefiles back to normal files; after this, the DEST repository can be used without largefiles at all. Use --verbose to print the parsed tree before and after aliases expansion. Use -C/--clean to reset the working directory branch to that of the parent of the working directory, negating a previous branch change. Use -d/--default to disable current configuration. Use -n/--none to deactivate guards (no other arguments needed). When no guards are active, patches with positive guards are skipped and patches with negative guards are pushed. Use -s/--series to print a list of all guards in the series file (no other arguments needed). Use -v for more information. Use :hg:`diff` if you only want to see the changes made since the last qrefresh, or :hg:`export qtip` if you want to see changes made by the current patch without including changes made since the qrefresh. Use :hg:`incoming` if you want to see what would have been added by a pull at the time you issued this command. If you then decide to add those changes to the repository, you should use :hg:`pull -r X` where ``X`` is the last changeset listed by :hg:`incoming`. Use null as the changeset to remove the working directory (like :hg:`clone -U`). Use the --no-backup option to discard the backup bundle once the operation completes. Use the -g/--git option to generate diffs in the git extended diff format. For more information, read :hg:`help diffs`. Use the -g/--git option to generate diffs in the git extended diff format. See :hg:`help diffs` for more information. Use the -g/--git option to keep the patch in the git extended diff format. Read the diffs help topic for more information on why this is important for preserving permission changes and copy/rename information. Use the -s/--similarity option to detect renamed files. This option takes a percentage between 0 (disabled) and 100 (files must be identical) as its parameter. With a parameter greater than 0, this compares every removed file with every added file and records those similar enough as renames. Detecting renamed files this way can be expensive. After using this option, :hg:`status -C` can be used to check which files were identified as moved or renamed. If not specified, -s/--similarity defaults to 100 and only renames of identical files are detected. Use the :hg:`qguard` command to set or print guards on patch, then use qselect to tell mq which guards to use. A patch will be pushed if it has no guards or any positive guards match the currently selected guard, but will not be pushed if any negative guards match the current guard. For example:: Use the command :hg:`update` to switch to an existing branch. Use the command :hg:`update` to switch to an existing branch. Use :hg:`commit --close-branch` to mark this branch as closed. Useful to prevent inadvertent keyword expansion and to speed up execution by including only files that are actual candidates for expansion. Using the -r/--rev or -d/--date options, revert the given files or directories to their states as of a specific revision. Because revert does not change the working directory parents, this will cause these files to appear modified. This can be helpful to "back out" some or all of an earlier change. See :hg:`backout` for a related method. Valid fields are most regular revision fields and some special fields. Valid types are: Verify the integrity of the current repository. When REV is not given, print a summary of the current state of the repository. When a merge is needed, the working directory is first updated to the newly pulled changes. Local changes are then merged into the pulled changes. To switch the merge order, use --switch-parent. When no files are specified, "hg shelve" saves all not-clean files. If specific files or directories are named, only changes to those files are shelved. When repositories are cloned locally, their data files will be hardlinked so that they only use the space of a single repository. When two revision arguments are given, then changes are shown between those revisions. If only one revision is specified then that revision is compared to the working directory, and, when no revisions are specified, the working directory files are compared to its parent. Whitespace between the above elements is ignored. With --debug, the source (filename and line number) is printed for each config item. With --edit, start an editor on the user-level config file. With --global, edit the system-wide config file. With --local, edit the repository-level config file. With --graph the revisions are shown as an ASCII art DAG with the most recent changeset at the top. 'o' is a changeset, '@' is a working directory parent, 'x' is obsolete, and '+' represents a fork where the changeset from the lines below is a parent of the 'o' merge on the same line. With --outgoing, this edits changesets not found in the destination repository. If URL of the destination is omitted, the 'default-push' (or 'default') path will be used. With -A/--all and -v/--verbose the codes used to show the status of files are:: With -b/--bundle, changesets are selected as for --outgoing, but a single email containing a binary Mercurial bundle as an attachment will be sent. With -f/--force, an existing patch of the same name will be overwritten. With -m/--mbox, instead of previewing each patchbomb message in a pager or sending the messages directly, it will create a UNIX mailbox file with the patch emails. This mailbox file can be previewed with any mail user agent which supports UNIX mbox files. With -n/--test, all steps will run, but mail will not be sent. You will be prompted for an email recipient address, a subject and an introductory message describing the patches of your patchbomb. Then when all is done, patchbomb messages are displayed. If the PAGER environment variable is set, your pager will be fired up once for each patchbomb message, so you can verify everything is alright. With -o/--outgoing, emails will be generated for patches not found in the destination repository (or only those which are ancestors of the specified revisions if any are provided) With -s/--similarity, hg will attempt to discover renames and copies in the patch in the same way as :hg:`addremove`. With -v, print file permissions, symlink and executable bits. With --debug, print file revision hashes. With five args, set a key to new if it currently is set to old. Reports success or failure. With multiple arguments, print names and values of all config items with matching section names. With no argument, show the current branch name. With one argument, set the working directory branch name (the branch will not exist in the repository until the next commit). Standard practice recommends that primary development take place on the 'default' branch. With no argument, show the phase name of specified revisions. With no arguments, displays the list of obsolescence markers. With no arguments, print a list of commands with short help messages. With no arguments, print names and values of all config items. With no arguments, print the currently active guards. With arguments, set guards for the named patch. With no arguments, prints the currently active guards. With one argument, sets the active guard. With no arguments, show all open branch heads in the repository. Branch heads are changesets that have no descendants on the same branch. They are where development generally takes place and are the usual targets for update and merge operations. With no revision specified, revert the specified files or directories to the contents they had in the parent of the working directory. This restores the contents of files to an unmodified state and unschedules adds, removes, copies, and renames. If the working directory has two parents, you must explicitly specify a revision. With one argument of the form section.name, print just the value of that config item. With one argument, renames the current patch to PATCH1. With two arguments, renames PATCH1 to PATCH2. With one of -p/--public, -d/--draft or -s/--secret, change the phase value of the specified revisions. With the --remote option, this will check the default paths for incoming and outgoing changes. This can be time-consuming. With the --switch-parent option, the diff will be against the second parent. It can be useful to review a merge. With the -d/--diffstat option, if the diffstat program is installed, the result of running diffstat on the patch is inserted. With the -d/--diffstat or --confirm options, you will be presented with a final summary of all messages and asked for confirmation before the messages are sent. With two args, list the keys in the given namespace. Without argument, pops off the top of the patch stack. If given a patch name, keeps popping off patches until the named patch is at the top of the stack. Without the -a/--text option, annotate will avoid processing files it detects as binary. With -a, annotate will annotate the file anyway, although the results will probably be neither useful nor desirable. Without the -a/--text option, diff will avoid generating diffs of files it detects as binary. With -a, diff will generate a diff anyway, probably with undesirable results. Without the -a/--text option, export will avoid generating diffs of files it detects as binary. With -a, export will generate a diff anyway, probably with undesirable results. You can change compression method with the -t/--type option. The available compression methods are: none, bzip2, and gzip (by default, bundles are compressed using bzip2). You can import a patch straight from a mail message. Even patches as attachments work (to use the body part, it must have type text/plain or text/x-patch). From and Subject headers of email message are used as default committer and commit message. All text/plain body parts before first diff are added to commit message. You can optionally mark selected transplanted changesets as merge changesets. You will not be prompted to transplant any ancestors of a merged transplant, and you can merge descendants of them normally instead of transplanting them. You can register an existing patch inside the patch directory with the -e/--existing flag. You can rewrite the changelog message with the --filter option. Its argument will be invoked with the current changelog message as $1 and the patch as $2. You can specify which changesets to rebase in two ways: as a "source" changeset or as a "base" changeset. Both are shorthand for a topologically related set of changesets (the "source branch"). If you specify source (``-s/--source``), rebase will rebase that changeset and all of its descendants onto dest. If you specify base (``-b/--base``), rebase will select ancestors of base back to but not including the common ancestor with dest. Thus, ``-b`` is less precise but more convenient than ``-s``: you can specify any changeset in the source branch, and rebase will select the whole branch. If you specify neither ``-s`` nor ``-b``, rebase uses the parent of the working directory as the base. You can use OpenSSL's CA certificate file if your platform has one. On most Linux systems this will be ``/etc/ssl/certs/ca-certificates.crt``. Otherwise you will have to generate this file manually. The form must be as follows:: You should not rebase changesets that have already been shared with others. Doing so will force everybody else to perform the same rebase or they will end up with duplicated changesets after pulling in your rebased changesets. 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:: [bar] eggs=ham green= eggs [bugzilla] bzurl=http://my-project.org/bugzilla user=bugmail@my-project.org password=plugh version=xmlrpc template=Changeset {node|short} in {root|basename}. {hgweb}/{webroot}/rev/{node|short}\n {desc}\n strip=5 [bugzilla] bzurl=http://my-project.org/bugzilla user=bugmail@my-project.org password=plugh version=xmlrpc+email bzemail=bugzilla@my-project.org template=Changeset {node|short} in {root|basename}. {hgweb}/{webroot}/rev/{node|short}\n {desc}\n strip=5 [bugzilla] host=localhost password=XYZZY version=3.0 bzuser=unknown@domain.com bzdir=/opt/bugzilla-3.2 template=Changeset {node|short} in {root|basename}. {hgweb}/{webroot}/rev/{node|short}\n {desc}\n strip=5 [committemplate] changeset = {desc}\n\n HG: Enter commit message. Lines beginning with 'HG:' are removed. HG: {extramsg} HG: -- HG: user: {author}\n{ifeq(p2rev, "-1", "", "HG: branch merge\n") }HG: branch '{branch}'\n{if(currentbookmark, "HG: bookmark '{currentbookmark}'\n") }{subrepos % "HG: subrepo {subrepo}\n" }{file_adds % "HG: added {file}\n" }{file_mods % "HG: changed {file}\n" }{file_dels % "HG: removed {file}\n" }{if(files, "", "HG: no files changed\n")} [extensions] bugzilla = [foo] eggs=large ham=serrano eggs=small [foo] ham=prosciutto eggs=medium bread=toasted [graph] # 2px width default.width = 2 # red color default.color = FF0000 [hooks] # run bugzilla hook on every change pulled or pushed in here incoming.bugzilla = python:hgext.bugzilla.hook [hostfingerprints] hg.intevation.org = fa:1f:d9:48:f1:e7:74:30:38:8d:d8:58:b6:94:b8:58:28:7d:8b:d0 [keyword] # expand keywords in every python file except those matching "x*" **.py = x* = ignore [keywordset] # prefer svn- over cvs-like default keywordmaps svn = True [paths] my_path = http://example.com/path [spam] eggs=ham green= eggs [spam] eggs=large ham=serrano eggs=small [usermap] user@emaildomain.com=user.name@bugzilladomain.com [web] baseurl=http://my-project.org/hg [websub] issues = s|issue(\d+)|issue\1|i italic = s/\b_(\S+)_\b/\1<\/i>/ bold = s/\*\b(\S+)\b\*/\1<\/b>/ ``--tool`` can be used to specify the merge tool used for file merges. It overrides the HGMERGE environment variable and your configuration files. See :hg:`help merge-tools` for options. ``ls`` Use Python's built-in instrumenting profiler. This profiler works on all platforms, but each line number it reports is the first line of a function. This restriction makes it difficult to identify the expensive parts of a non-trivial function. ``stat`` Use a third-party statistical profiler, statprof. This profiler currently runs only on Unix systems, and is most useful for profiling commands that run for longer than about 0.1 seconds. ``metadata`` is the default field which is used when no fields are specified. You can match more than one field at a time. ``text`` Generate a profiling report. When saving to a file, it should be noted that only the report is saved, and the profiling data is not kept. ``kcachegrind`` Format profiling data for kcachegrind use: when saving to a file, the generated file can directly be loaded into kcachegrind. aliases: %s bar.prefix = secure.example.org bar.key = path/to/file.key bar.cert = path/to/file.cert bar.schemes = https committer = Bugzilla user foo.prefix = hg.intevation.org/mercurial foo.username = foo foo.password = bar foo.schemes = http https hg add/remove/copy/rename work as usual, though you might want to use git-style patches (-g/--git or [diff] git=1) to track copies and renames. See the diffs help topic for more information on the git diff format. hg forget "set:hgignore() and not ignored()" hg locate "set:**.c and not encoding('UTF-8')" hg locate "set:grep(magic) and not binary()" hg log -r "(keyword(bug) or keyword(issue)) and not ancestors(tag())" hg log -r "1.3::1.5 and keyword(bug) and file('hgext/*')" hg log -r "branch(default) and 1.5:: and not merge()" hg log -r "branch(default)" hg log -r "head() and not closed()" hg log -r "sort(date('May 2008'), user)" hg push my_path hg remove "set: 'listfile:foo.lst' and (**a* or **b*)" hg revert "set:copied() and binary() and size('>1M')" hg status -A "set:binary()" http://server/(.*)-hg/ = http://hg.server/\1/ kwexpand refuses to run if given files contain local changes. kwshrink refuses to run if given files contain local changes. latest = log --limit 5 patternname = s/SEARCH_REGEX/REPLACE_EXPRESSION/[i] qnew creates a new patch on top of the currently-applied patch (if any). The patch will be initialized with any outstanding changes in the working directory. You may also use -I/--include, -X/--exclude, and/or a list of files after the patch name to add only changes to matching files to the new patch, leaving the rest as uncommitted modifications. qselect can change the guards on applied patches. It does not pop guarded patches by default. Use --pop to pop back to the last applied patch that is not guarded. Use --reapply (which implies --pop) to push back to the current patch afterwards, but skip guarded patches. ssh://example.com//tmp/repository stable5 = latest -b stable where "original_branch_name" is the name of the branch in the source repository, and "new_branch_name" is the name of the branch is the destination repository. No whitespace is allowed in the branch names. This can be used to (for instance) move code in one repository from "default" to a named branch. $ hg log --template "{bookmarks % '{bookmark}{ifeq(bookmark, current, \"*\")} '}\n" $ hg log --template "{ifcontains(rev, revset('.'), '@')}\n" $ hg log --template "{splitlines(desc) % '**** {line}\n'}" $ hg log --template "{startswith(\"template\", firstline(desc))}\n" $ hg log --template "{word(\"0\", desc)}\n" $ hg log -r 0 --template "files: {join(files, ', ')}\n" $ hg log -r 0 --template "files:\n{files % ' {file}\n'}" $ hg log -r 0 --template "{date(date, '%Y')}\n" $ hg log -r 0 --template "{fill(desc, '30')}" $ hg log -r 0 --template "{ifeq(branch, 'default', 'on the main branch', 'on branch {branch}')}\n" $ hg log -r 0 --template "{join(extras, '\n')}\n" $ hg log -r 0 --template "{label('changeset.{phase}', node|short)}\n" $ hg log -r 0 --template "{sub(r'^.*\n?\n?', '', desc)}\n" $ hg tip --template "{date|isodate}\n" 2008-08-21 18:22 +0000 $ hg tip --template "{if(author, '{author}\n')}" @ 6[tip] 038383181893 2009-04-27 18:04 -0500 stefan | Add theta | o 5 140988835471 2009-04-27 18:04 -0500 stefan | Add eta | o 4 122930637314 2009-04-27 18:04 -0500 stefan | Add zeta | o 3 836302820282 2009-04-27 18:04 -0500 stefan | Add epsilon | o 2 989b4d060121 2009-04-27 18:04 -0500 durin42 | Add beta and delta. | o 1 081603921c3f 2009-04-27 18:04 -0500 durin42 | Add gamma | o 0 d8d2fcd0e319 2009-04-27 18:04 -0500 durin42 Add alpha After selecting a merge program, Mercurial will by default attempt to merge the files using a simple merge algorithm first. Only if it doesn't succeed because of conflicting changes Mercurial will actually execute the merge program. Whether to use the simple merge algorithm first can be controlled by the premerge setting of the merge tool. Premerge is enabled by default unless the file is binary or a symlink. Changesets in secret phase are not exchanged with the server. This applies to their content: file names, file contents, and changeset metadata. For technical reasons, the identifier (e.g. d825e4025e39) of the secret changeset may be communicated to the server. Environment variables with empty values may not be passed to hooks on platforms such as Windows. As an example, ``$HG_PARENT2`` will have an empty value under Unix-like platforms for non-merge changesets, while it will not be available at all under Windows. For example, if multibyte character ending with backslash (0x5c) is followed by ASCII character 'n' in the customized template, sequence of backslash and 'n' is treated as line-feed unexpectedly (and multibyte character is broken, too). For some problematic encodings (see :hg:`help win32mbcs` for detail), this customization should be configured carefully, to avoid showing broken characters. Git and Subversion subrepos are also supported:: It is generally better to use standard hooks rather than the generic pre- and post- command hooks as they are guaranteed to be called in the appropriate contexts for influencing transactions. Also, hooks like "commit" will be called in all contexts that generate a commit (e.g. tag) and not just the commit command. It is possible to create aliases with the same names as existing commands, which will then override the original definitions. This is almost always a bad idea! Note that ``.hgsub`` does not exist by default in Mercurial repositories, you have to create and add it to the parent repository before using subrepositories. Some global configuration options such as ``-R`` are processed before shell aliases and will thus not be passed to aliases. The more specific you are in your filename patterns the less you lose speed in huge repositories. The registry key ``HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mercurial`` is used when running 32-bit Python on 64-bit Windows. The rules will first apply when files are touched in the working copy, e.g. by updating to null and back to tip to touch all files. 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. echo = !echo $@ purge = !$HG status --no-status --unknown -0 | xargs -0 rm where ``path/to/nested`` is the checkout location relatively to the parent Mercurial root, and ``https://example.com/nested/repo/path`` is the source repository path. The source can also reference a filesystem path. # 'none' turns off all effects status.clean = none status.copied = none # 1) only 'gollum' can commit to branch 'ring'; # 'gollum' and anyone else can still commit to any other branch. ring = !gollum # 2) only members of the group 'hobbit' can commit to branch 'lake'; # 'hobbit' members and anyone else can still commit to any other branch. lake = !@hobbit # A bad user is denied on all branches: * = bad-user # A few users are allowed on branch-a: branch-a = user-1, user-2, user-3 # Changing the priority of preconfigured tool vimdiff.priority = 0 # Define new tool myHtmlTool.args = -m $local $other $base $output myHtmlTool.regkey = Software\FooSoftware\HtmlMerge myHtmlTool.priority = 1 # Everyone (except for "user6" and "@hg-denied" - see acl.deny above) # will have write access to any file under the "resources" folder # (except for 1 file. See acl.deny): src/main/resources/** = * # Everyone is allowed on branch-for-tests: branch-for-tests = * # Everyone is denied to the frozen branch: frozen-branch = * # Group "hg-denied" will not have write access to any file: ** = @hg-denied # Nobody will be able to change "DONT-TOUCH-THIS.txt", despite # everyone being able to change all other files. See below. src/main/resources/DONT-TOUCH-THIS.txt = * # Only one user is allowed on branch-b: branch-b = user-1 # The super user is allowed on any branch: * = super-user # To match everyone, use an asterisk for the user: # my/glob/pattern = * # Use this if you want to check access restrictions at commit time pretxncommit.acl = python:hgext.acl.hook # Use this if you want to check access restrictions for pull, push, # bundle and serve. pretxnchangegroup.acl = python:hgext.acl.hook # User "doc_writer" has write access to any file under the "docs" # folder: docs/** = doc_writer # User "jack" and group "designers" have write access to any file # under the "images" folder: images/** = jack, @designers # You can also deny access based on file paths: # add new command called meld, runs meld (no need to name twice) meld = # add new command called vdiff, runs kdiff3 vdiff = kdiff3 # add new command called vimdiff, runs gvimdiff with DirDiff plugin # (see http://www.vim.org/scripts/script.php?script_id=102) Non # English user, be sure to put "let g:DirDiffDynamicDiffText = 1" in # your .vimrc vimdiff = gvim -f "+next" \ "+execute 'DirDiff' fnameescape(argv(0)) fnameescape(argv(1))" # one email for all outgoing changesets outgoing.notify = python:hgext.notify.hook # switch to regexp syntax. syntax: regexp ^\.pc/ # use glob syntax. syntax: glob # user6 will not have write access to any file: ** = user6 $ cd test $ hg serve $ dd if=/dev/urandom of=randomdata count=2000 $ hg add --large randomdata $ hg commit -m 'add randomdata as a largefile' $ hg add --lfsize 2 $ hg lfconvert --size 10 oldrepo newrepo $ hg paths zc-test = http://example.com:8000/test $parent1, $plabel1 - filename, descriptive label of first parent $child, $clabel - filename, descriptive label of child revision $parent2, $plabel2 - filename, descriptive label of second parent $root - repository root $parent is an alias for $parent1. %include ~/.hgrc.d/$HOST.rc %s in %s should not have %s line endings *.elc *.pyc *~ - web - paths - collections -f -> ::. -d x -> date(x) -k x -> keyword(x) -m -> merge() -u x -> user(x) -b x -> branch(x) -P x -> !::x -l x -> limit(expr, x) .hgtags = release_engineer :``serve``: changesets received via http or ssh :``pull``: changesets received via ``hg pull`` :``unbundle``: changesets received via ``hg unbundle`` :``push``: changesets sent or received via ``hg push`` :``bundle``: changesets sent via ``hg unbundle`` :``xmlrpc``: Bugzilla XMLRPC interface. :``xmlrpc+email``: Bugzilla XMLRPC and email interfaces. :``3.0``: MySQL access, Bugzilla 3.0 and later. :``2.18``: MySQL access, Bugzilla 2.18 and up to but not including 3.0. :``2.16``: MySQL access, Bugzilla 2.16 and up to but not including 2.18. :``{bug}``: The Bugzilla bug ID. :``{root}``: The full pathname of the Mercurial repository. :``{webroot}``: Stripped pathname of the Mercurial repository. :``{hgweb}``: Base URL for browsing Mercurial repositories. = Alternatively specify "ssh -C" as your ssh command in your configuration file or with the --ssh command line option. An alternative syntax is ``x..y``. Default ``changeset {node|short} in repo {root} refers to bug {bug}.\ndetails:\n\t{desc|tabindent}`` Default: serve. Deprecation: The win32text extension requires each user to configure the extension again and again for each clone since the configuration is not copied when cloning. Patterns specified in ``.hgignore`` are not rooted. Please see :hg:`help hgignore` for details. Patterns specified in other than ``.hgignore`` are always rooted. Please see :hg:`help patterns` for details. Pulling a draft changeset from a publishing server does not mark it as public on the server side due to the read-only nature of pull. See also the ``[usermap]`` section. Servers running older versions of Mercurial are treated as publishing. We have therefore made the ``eol`` as an alternative. The ``eol`` uses a version controlled file for its configuration and each clone will therefore use the right settings from the start. [acl.allow.branches] [acl.allow.branches] # Empty [acl.allow] # Empty [acl.allow] # if acl.allow is not present, all users are allowed by default # empty acl.allow = no users allowed [acl.deny.branches] [acl.deny] # 3) only 'gollum' can change the file below; # 'gollum' and anyone else can still change any other file. /misty/mountains/cave/ring = !gollum [acl.deny] # This list is checked first. If a match is found, acl.allow is not # checked. All users are granted access if acl.deny is not present. # Format for both lists: glob pattern = user, ..., @group, ... [acl] # Allow or deny access for incoming changes only if their source is # listed here, let them pass otherwise. Source is "serve" for all # remote access (http or ssh), "push", "pull" or "bundle" when the # related commands are run locally. # Default: serve sources = serve [blackbox] # limit the size of a log file maxsize = 1.5 MB # rotate up to N log files when the current one gets too big maxfiles = 3 [blackbox] track = * [blackbox] track = command, commandfinish, commandexception, exthook, pythonhook [blackbox] track = incoming [cia] # your registered CIA user name user = foo # the name of the project in CIA project = foo # the module (subproject) (optional) #module = foo # Append a diffstat to the log message (optional) #diffstat = False # Template to use for log messages (optional) #template = {desc}\n{baseurl}{webroot}/rev/{node}-- {diffstat} # Style to use (optional) #style = foo # The URL of the CIA notification service (optional) # You can use mailto: URLs to send by email, e.g. # mailto:cia@cia.vc # Make sure to set email.from if you do this. #url = http://cia.vc/ # print message instead of sending it (optional) #test = False # number of slashes to strip for url paths #strip = 0 [color] mode = terminfo [color] status.modified = blue bold underline red_background status.added = green bold status.removed = red bold blue_background status.deleted = cyan bold underline status.unknown = magenta bold underline status.ignored = black bold [decode] # recompress gzip files when writing them to the working dir (we # can safely omit "pipe:", because it's the default) *.gz = gzip [decode] ** = cleverdecode: # or ** = macdecode: [defaults] log = -v status = -m [diff-tools] kdiff3.diffargs=--L1 '$plabel1' --L2 '$clabel' $parent $child [email] from = Joseph User method = /usr/sbin/sendmail # charsets for western Europeans # us-ascii, utf-8 omitted, as they are tried first and last charsets = iso-8859-1, iso-8859-15, windows-1252 [email] from = My Name to = recipient1, recipient2, ... cc = cc1, cc2, ... bcc = bcc1, bcc2, ... reply-to = address1, address2, ... [encode] # uncompress gzip files on checkin to improve delta compression # note: not necessarily a good idea, just an example *.gz = pipe: gunzip [extdiff] # add new command that runs GNU diff(1) in 'context diff' mode cdiff = gdiff -Nprc5 ## or the old way: #cmd.cdiff = gdiff #opts.cdiff = -Nprc5 [extdiff] kdiff3 = [extensions] # (the progress extension will get loaded from Mercurial's path) progress = # (this extension will get loaded from the file specified) myfeature = ~/.hgext/myfeature.py [extensions] # disabling extension bar residing in /path/to/extension/bar.py bar = !/path/to/extension/bar.py # ditto, but no path was supplied for extension baz baz = ! [extensions] foo = [extensions] myfeature = ~/.hgext/myfeature.py [extensions] win32text = [encode] ** = cleverencode: # or ** = macencode: [factotum] executable = /bin/auth/factotum mountpoint = /mnt/factotum service = hg [hgk] path=/location/of/hgk [hgk] vdiff=vdiff [hooks] [hooks] # one email for each incoming changeset incoming.notify = python:hgext.notify.hook # one email for all incoming changesets changegroup.notify = python:hgext.notify.hook [hooks] # one of these: changegroup.cia = python:hgcia.hook #incoming.cia = python:hgcia.hook [hooks] # update working directory after adding changesets changegroup.update = hg update # do not use the site-wide hook incoming = incoming.email = /my/email/hook incoming.autobuild = /my/build/hook # force autobuild hook to run before other incoming hooks priority.incoming.autobuild = 1 [hooks] pretxnchangegroup.crlf = python:hgext.win32text.forbidcrlf # or pretxnchangegroup.cr = python:hgext.win32text.forbidcr [hooks] pretxncommit.crlf = python:hgext.win32text.forbidcrlf # or pretxncommit.cr = python:hgext.win32text.forbidcr [largefiles] minsize = 2 [largefiles] patterns = *.jpg re:.*\.(png|bmp)$ library.zip content/audio/* [merge-patterns] **.c = kdiff3 **.jpg = myimgmerge [merge-tools] # Override stock tool location kdiff3.executable = ~/bin/kdiff3 # Specify command line kdiff3.args = $base $local $other -o $output # Give higher priority kdiff3.priority = 1 [mq] git = auto/keep/yes/no [mq] keepchanges = True [mq] secret = True [notify] config = /path/to/subscriptionsfile [pager] attend = annotate, cat, diff, export, glog, log, qdiff [pager] attend-cat = false [pager] ignore = version, help, update [pager] pager = less -FRX [paths] /projects/a = /srv/tmprepos/a /projects/b = c:/repos/b / = /srv/repos/* /user/bob = /home/bob/repos/** [paths] alias1 = URL1 alias2 = URL2 ... [patterns] **.py = native **.vcproj = CRLF **.txt = native Makefile = LF **.jpg = BIN [phases] publish = False [progress] delay = 3 # number of seconds (float) before showing the progress bar changedelay = 1 # changedelay: minimum delay before showing a new topic. # If set to less than 3 * refresh, that value will # be used instead. refresh = 0.1 # time in seconds between refreshes of the progress bar format = topic bar number estimate # format of the progress bar width = # if set, the maximum width of the progress information # (that is, min(width, term width) will be used) clear-complete = True # clear the progress bar after it's done disable = False # if true, don't show a progress bar assume-tty = False # if true, ALWAYS show a progress bar, unless # disable is given [repository] native = LF [reposubs] # key is repo pattern, value is a comma-separated list of subscriber emails pattern = user@host [reposubs] */widgets#branch(release) = qa-team@example.com [revsetalias] h = heads() d($1) = sort($1, date) rs($1, $2) = reverse(sort($1, $2)) [schemes] gcode = http://{1}.googlecode.com/hg/ [schemes] py = http://code.python.org/hg/ [schemes] py = http://hg.python.org/ bb = https://bitbucket.org/ bb+ssh = ssh://hg@bitbucket.org/ gcode = https://{1}.googlecode.com/hg/ kiln = https://{1}.kilnhg.com/Repo/ [ui] username = Firstname Lastname verbose = True [usersubs] # key is subscriber email, value is a comma-separated list of repo patterns user@host = pattern [web] # If you want hyperlinks (optional) baseurl = http://server/path/to/repo [web] pygments_style =