_!!43R(53 > W es''-4;S0(,:2Q4)%# -Oe]NAbM37&:^?@JGe*c:</wOX6P T  $ "    x l  hpC=2p !3..!=_*z/](3[\"SM]T(rR'zmp P! "B"##{$x%w&M($(2"*MU+Z,i-h..//[T0X0c 1jm1^1^72_2;223/4*H4s4K]556667bR9W: ;~; <<q= >? @@CBFCD)DENF{HH)II>JlL(;MdMmN-O?)QiQFQ5RRS T<TTT[U_V<BWW!X|3XkXMY5jYtZ[[[AG\~]l^u^r@__}@`h`f'aamzb^bGcddeeeefaag<g;hѺ:aR"Uu˽.qeelv&|6py_`^=3Cw#$c"}Fg6`^<XR] }=A'ik3V&}L#\WWPO f}&oh}IBm&h8_6]mxbaM Xb}a^Q- M WbrSuC. <LjFPFu"T%wBCM$8rLC@ OL=H=Lof t K >B G V > ~_  *  *6at#x$h%v<R!,N3N+z2Z+K ake&N_k0BO*/aO l n#t#-$X.$U$"$%%m% "&?,&dl&&'d){)`*h*Ld+e+D,?\,,/,5, - -*)-*T- ----- -- --6.1?.q.5. .0.* /5/;/IJ/W/W/UD0V0o0a1"j1*1*1%1 2"2*222 :2E2M2U2]2e2m2u2 {22 2 2!222 3 3!3I>3,33 33!34!*4"L4o4 4744 4 44 5 5 (5 35A5[5d5m5v555055150'6X6p66666-6*!7L7"`7)7$7+7&7%%8-K8(y8+8 8889939ME9O9F9 *:5:)D:(n:):*:*:';?;&Y;+;%; ;&;<3< N<!o< <<,<:< =@=_=t====1==>>30>d>#}>>>>> ?!?2?N?*d???'??"?%@D@W@m@2@&@*@" A+0A+\AAAAAAB5BTBqBtB}BB'BB BBBB B CC,C$4CYC^C+wCICC+ D5D)QD{D&D'DD(D('E+PE6|EAE"EF51FgF3F(F7F)GEGTG"fGG*G G0G< HJH]HFxHFH4I$;I>`I}IJ3JJLKK0 LQL MN[O.cP7QXQk#RR S>;S4zS$SES#T1>T%pT+TT%TqTiU)U8'V`V1}VVLW\W5XXY.Z1ZZa[t4\\\8]?]04^Me^Q^_:__Caob5bbocddCXede;fU=fnf=g>@gUg7g7 h5Eh{hh ioriiRjjRek<k0kW&l=~lXlmam)n@n>Qoyou pkpp3qrjs=ss=Et6tFtku?muAugvTWwIwwcxSxLy9zz,{I|o|k~D9$#Pƃ ""+N0ʆ'݆?ME#S!Wy(8^B`/ӊ  @ɋ BCZh<AD?5Kc#} $q CHOb\rϓ ^ kHy–P`i.B"(e ˙ O [JӞBE_, 9)$,Q(E"}h9rb IL_<|q>S0-x4P۱L>?G JTn@O  ;ŷ%ɷTN?CK4T'ؼ*#1@)r*ý&l';ľKKLK5* $@-=?=}!=Rp,Jx_1}[fj-'#% ?JGc'&w)cG2C[fzW(#"<m_(Nw^SN*y*.Y8t 4Q5=QQnZT uarDerDClC n.M7S\noYX>P!V/xS$kXRW~)48m&!6Ih 82;Mi< 3  9) cmt64Pcy ) *F %q B 4 P K` 2 H w( < %  7 L UY O 1 D1Gv-)0:B?U>\@?/>LH&723xfNO.b~K0-F^kHOZ*E7S6.OJ3N)$GQlLr m~ ;G5(D3m6'*(>(g*,-49n   . 6B .y 5 3 :!M!]!#y!!#!1!H"+X""""6"*"2*#0]#0#.#2#!$ :$E$_$y$$$$$.$ %,$%Q%b%"w%%%"%*%&%4&Z&o& &&+&&&'2'O' a'''#'4'2(-F( t((*( ((#(#)(),A)(n)))1)))* **<*#Z*#~*'*%*&*9+#Q+u++++ +>+.,(J,s,,,%,,4,"1-T-e-v- --<-<- .:. K. W.d.,x.(.(../!)/lK/./e/M0G0d1:~1;242A*3@l44DS5X5I5;6B6%7'.7V7pu77(7828J8_85{8!8%88$9;9"M9#p99;9%9 :&3:#Z:~:/: :?:$!;F;d;;;$;'; <+%<&Q<'x<!<'<&<&=!8=&Z==,=-=#=!>(>>g>>$>'>/>!? A?b?#~?)??/?$@*@@k@#@@"@@.A7ABJA9A$AA(B#,BPBlBB&B'B!BC *C:KC2C.C-C)D+@D'lD"D%DfD.DE&sE*E#E*E"F*7F;bF;F$F3F3G(OGxG(G(GG$GH5H$NHsH0H"HKH'-IUUII IIIII JJ.JEJ[JbJ{J JJ)J,J'KGK`KzKKK%K KLL"1LTL7lL<L0L6M9IM8M,M<M&&N3MN NN5N#N NOO^T^p^^#^+^'^_/;_k_'_"_)_B_"B`e`)x``>`/`)aIa*Oa'zaaa4abb /b Pb\b&nbb/b"bc)c0Hcycc)cc cc dd.dGd_d"sdd*d?de0e!Ieke+eeeeef*f>f^f'yf/fff,f-'g)Uggg/g(g h&'hNh`h&yhhhhh&h.iKi_ixiii#ii1i!-j'Ojwj-jj j#jkk;kLk\krkkkkkk(l,l1Gl4yl8lllllm'm=m!\m,~m mm<mn2n(Bn kn-nCn8n7oJo&Po wo oDo o+o)p-2p`p opypp$p)pp p qq+q GqUqhqxq}qqq qq!q*rBrUr urrr-r*rs s8's`s5|ss3s-t'0tXtht$tt#ttu!u23ufu.}u+u!u u!v#=vavxvv#v vvw3w/Lw|w8ww w0w "x!0x Rx0`x&x=xxy5+y!ayy yyyyy&z.zIz^zxzzz49{n|&|)|'|3|:.}*i}:} }!}~.~,K~x~~~/~~+(<'e!!>,[(: $ @=_' Ł  >)_*Ԃ! )+U*k)ۃ(B'_!!Ʉ395Y>9΅ (&I'p$#  9K+`!Ƈׇ(!Bd-ʈ9-g  ͉+?H?e86ފ4$Jo+x)["Վ  !$F#^'ď/Nm!$ڐ0"B-e"Ƒ'#5$E>jؒ%+(>3g?1N b9l7ؔ#(7`w9&ʕ1# C M%Z,- 77K+9->"l+!0,R6)Ǚ,4KHhT!#("L#o"3ɛ6>4$s!Ҝ5: N o ŝם 0Ng }4!A#ex$ȟ%ߟ*MD)à(<+R~+ȡ"*%M"s#>+>/j'ߣ +8V&g [) C6+z<#=-Es!9<>OarWWݧO589[*T1 ="A`}0=ê 38)l/%ƫ  %!C*e5*Ƭ'$s>6O#B"f"(-ծ<(@#i557S"l"4)%4<UWk!ñ (@-Y&ٲ(D"]**%!1$Sx#-ƴ"")#L$p)$е  7#G)k ?Զ!&60]  з:׷1-Q( !-:(hڹ2#&)J-t!!ĺ5,IQ kC&л2.ar)%/ ?"` 8ٽ" .H&W~&4*&=]|(  ܿ&#Jh~ %a7#'!#A3e'&$#(H&q7+-D a1kM;!' IS'g"O!@!b% '0$F$k&2 -?&Z )+;g z- 3Pi%848-!f+#'%+Qm%8 =")`(#*1G y " $#?*c/)$*  8&Y$  /9Ui$*(% !2Tr*,?**U nz)%*"Dg&#5%6'\ ) 8Yx-/- 9"U-x$5$;`#5:$Lq +0,-''U1}+2 +>"j.#&(H#c#+?&%f10Ng%%& ##.7R3! <\)u5$%&$Lq$.  "*!G%i%%&!#?'c)>+ $'L"` /!+F ],i,%EXe+ 0+Lx%5/>O),N46T$ 0*,W"v!w.s"(> Hd 8/10')X/:Kk)$@?_%5 C_v-,% 61hT&4 Q0\(Id|":P2o!*!I'k5R66H,[&/,> kK";U)i+?Om| 7R c %@0Ct"!.BLK0 13J6~.#3<OXn 0=E+5+B'T3|81Pl#2"9&\$;.)K"u#&,)+U t~ ?053f43@,Dq&4" $5=sB""? ![ 1} * & ( ;* -f a A ?8 x ! ( 4 6  K X w g 2 2' 'Z N @ RCeG*'(D+m3&( 35i/q'10z.:DZr.6>4 O\z.#87!4Y;0(,$:Q64)%"#HlBYVI]hGgKD@@IeH1.z}E'8mVZIXh '!D!_!*"C"T"r $$F%vU&M&'2'(*--7.?e./5050-141,Q1*~1w1!2z>22"2S2N3fU3+334VQ55Z6"7 88d9I::;P<<=MY>T?@C+CbDKFGu{IIJKd(L[LmL|WMmMpBNlN< O]O&]P'PP`Q-RRrSTTIVW^XXZ[f\]*_(E`n`MCbcdQe VfswghiajWkZkdYn/n<n+p> qCLss^?tt4uv wFw^wnw9x YyIfzz'o{{0|x|f<}~)[=wy voi)Ğhrx;O\BYBIXDy8z} : :vDPԟh]ƠnT[áe[(L}/ʥM+*-2l,;tݱ^RLWGܵ$j]|Fڸ:!\N?#qK9JDf#PϽG BhMT@NOJ߿*#I#mOE=@L~KL[dyM:dQA?A:@?jCIwe 71r<A4r$!/tCC,f1L~zF|uAGPZyc8x3A#eErG1${-B 55+}aPIR6g     e q  |&KF/7](=1|[{oo& m4, Ia!Z!}"}"<#?#l$|=%z%5&&'K())}*1+nK,,/ 01:2 4 546T66d7K7008a8*p8$8g9g(::~6<%=<=C?P\?L?`?[@9:ANtA[ABPBJ"CemCChD{@EEhWFQFCGdVHIHII4I+I0K8KKGKBMuN'NqN('OPOgOO  PsQ[RUVNVMWWXXY:YZYJZfZ |ZZik[[\_\]3]O]/f]B]*]/^a4^^2^ab-bTb[c"lcc>dmZd d?dseezf h7h(iviQUjejD k?Rkk/kIk l )l<3l3pllllll m m m+m+Em2qmm6m'mCn/[nnncnh ohsofogCpp+q&4q.[q4q0q2q#r+r3r ;rFrNrVr^rfrnrvr ~rr=r r#rs$s Bs Ms(Zs`s9st =tJt dt0t5t(tu*uN9uu u u#uu u uvv4v=vEvMvVv._vIv!v9vB4wwwww%wwx.+x/Zxxx%x)x'y"0y!Sy)uy$y'y yyz-zHzfz]zz]zP6{ {{0{0{+|3;|+o|/|#|-|-}.K}+z}+}}}#~!3~ U~$b~1~_~ !:+\>!6M<e1€%,,Hu,#Ё2;'c}.Ԃ 9?ZC9ރ86Q: Ä$#"Ad"}Å ҅<, IV]#c' Ɔ8І  *.HY 6Ç%2 S,rF-"29U5Hʼn.JGJA:?,z9̋*$ O0]*̌?X'?3C8ÎLڎK's1D7@OgOϘ"c?<ƙ9F=1B<*6a<q23D$!i;ǝOs &,ġ5Rob}F8'>`g]eGc:JxFb+fkAįK>Ӱ>wQ;ɱ;DAs&|`"a="K`S-Tַi>r)U{vBT@CEW[t3qlBg tk2s$#EHCidT# +(7`a 7TW{7(`$d, 4=BfX=31E;A JIX ddyKNj0BU]{ / -;<B IUog ILJCcwyz]*lM-jJC'*-OXa + 9_>ko<yT]T\MA0Izl8l&  S bI  X Z = G  )+gjo X=A J)T~3--J>x,"77J";'POxZ[#\?2"4W s +_Le'~G  0!"#JF$~&h'Ly(()ke++<,#,-&.(//Nh012$3$3-3-$4+R4~4. 5O5?8X8l9D9U?::h(;L<,<( =(4=f]=.==>(?@VFAA$BPB8D>EFFGHbJIK7XKKFKtKRLMM{AN{Nb9OvPJQ^QQmRRZSt6T TTuT4U&U W!Ww&W#WWXXY6[[\N]f]z]_<`FWaa83c{lddpet]ffecg?h i&iiii j)j >j=Lj8j;jjk 9k=Ekk4kk k?k&l/l6l8Glllllllm*mAmYmvm mm m.m"m.m,(n0UnWn:n\oavo?oIpbpMp0Cq&tq5r_rp1sMs2sU#tMyt-tt0uBuM9vHvov@wKwF4xG{x9xQxZOy9yRyR7z~zg {hq{w{NR|>|W|8}Y}E$~(j~\~F~72"^86f΀353iXX~O~΂Mm0 9QL,؅83>;r#Ȇ*# ;\?c@&7 C X d q#(Ɉ4>D?EÉC IM%/ϊ(2(?[V>1M kI9֌HJYEGD2 wȎ7+NCz0ُ 05f%+Ȑ!5Ld 5"!&"Be)|"-ɒ4;,9h> '9 P[-k.Δ-#+O6lǕ,.5?-u;;ߖ?K[/ח!!$FE_;*!  .%O8u4D)(Rp ?ʚ@ Kj H›3 9?y+ݜ-th MqޞP>k;3@[T_LZJ1% ~Fť.ͥ)/&V9lI%.E,c)Cӧ/<G37EA6xG3ݩN7`2=˪( 12GdD6I(>r>.=.]I-֭5":8]9-Ю,4+%`1--;9P3".6+G=s'>ٱ*4C$x,=ʲBK^eUij=!X<z@ "<@Y-1ȵ"#FA>IǶH>Z?<ٷ)1@}rF>7:vCI>?:~QN =ZK,2 D,e<ϼ-&;7[.0߽a3rV'B\c|п ؿ! !<@^.!0CR"6%=\1+8F1:xA41*&\\%&D^um&"<i_'#&@(_8>2<3 p }!Oh"=, /:/j+#+'9>#x#"1/(En:$?-)'W (C/Isj($84]"1 :<:w.0o!;'&"?"b7!.8Vs" >,Q;~>@+:f &)fF`5x,&1"T1h>2 2(-[><T&s+-K9S89/8WGn# !')Is! 8>%d{3$ +@_w)+0G"\2,(:&C,j!#% 6-W9$4589n:'.A%p.!6/V<-11_!B*7!Y/v6-$,Qg(}#10N56: E M Waj0)@;QBm.641;fS>5L1U b +:IU  )":L ' (!C!e+/+?Pf5@ U%{56-"'Px$##B7T64"!2"T$w!#!@[{0> 22@ s! 0'? Je6$  :B)b"##: /))Y1<?OO$# C)m%80 4;6p/ &"A,\, 9-;?{>!)R0h+&((17Z:$# $-;R54"$5*Z9$#"'B8jG>B*9m-(=0<(m5  ( 2 G .a &   * * B ^ (| " 9   ; Z m L #  . #; &_ 0  $    , aF P 7 B12t*# ,/\88'S{6'/#(>+g$+"'0:0k$ 2"(8a"/- ;:W"4|3.6IAD'"Cf ?%K'*s&9$($8M/=$)9A-{7AB VwF&!R"uO4.$Ch;{#(# @: G{  > !A5!w!!^!y "-""""##:4#Mo#W#K$5a$$$:$M%S%%m%#%%%"% &%&'?&g&J&$&!&-'C':\''+'A'(1(1K("}((*(((*)w?))) )&)*<*T*m**.**/*!+33+#g++&+6+ ,#%,I,(^,.,B,4,3.-!b-8----. .%.E.3T...n.C#/_g///;//30;c0=00+0F!1Eh1611%1"2?2]Y2`2T3:m3:3|3,`4C44O4&05WW5'55:5A,6)n66@696A-70o77777,75$8DZ8?8-8* 989@9 9j:+p:#:1:0:J#;=n;*;-;*<;0</l<7<&< <.=5K=H=B= >&>9>*@>!k>p>+>"*? M?X?u??*?'??@,@%K@q@(@@,@@?A;QA3AA&A4B=B+YBB?BB2B5+C'aC(CC4C<C5D.UDD,DBD.E ?E(LETuE1E&EH#F0lF'FF?F" G+0G\G%yG+G+GG1H&IH/pH0H.HII3I7RI(I7I3I)J-IJ=wJ@J JK($K^MK.KK KULkL{LL!L3L)M5/M'eM0MMMPMNN*gN'N NN-NO36O@jO?O*O)P,@P mP-P*PPP)QI>Q Q*Q!Q!QR/RBR XR&eRRRsR26S+iSS?S S#S+ T:LT7T%T-T1U,EU7rU.UUJU=DV1V!VV^Vn>WEW1W%X7X/UX2X/X3XbY+Y)Y&Y.Y +Z 6ZDZ._Z:Z)Z!Z.[ED[[$[9[#[1\P\ n\{\\$\\!\6]BG]]]8]&]%^E^"V^y^"^&^^*^9'_:a_?_C_! `9B`|`7``3`.$a#SawaaFaMa2b$Pb4ub8b4bc1cKc5ic6c@c(d@d!Sdud1~d#d/de0#e9Te*e.e&e5f*Ef0pfffffg"g@g=Ug gggg,g3hLh;ih(h!hh iB'iBjiMi/i +jLj[j5sjj'j/j=!k+_k)k&k)k ll#l9l6?lvl1l#ll lm7=mum#m!m*m6n4=n<rn nn"n:oJoPo$boCo9o>p=Dp/pp$pQpGDq?qqqq.r<7r4tr;r'r@ sNs8es9s(s3t85tntBt,t(t-&u Tu1uuu,u'uv=;vFyv0v"v2wGw"`ww'wwwx(x1Ex$wx+xx.xEy;Ly1y&yy zL zXzIxzBz{.{'L{5t{3{{){'|LF||/| |#|*}-2}1`}#}+}1}$~'9~9a~1~S~;!]6d-'( 3'$[ 3Հ ;,9< v:(ҁ3/lO6ڂ,&'S+{ǃ܃0;%a5yCFB:Q}(υ+*$O#gEц0:(R3{ć!ه2#Έ(=;*y" ljEԉ53PB7NJ:W%v(ŋڋ ,"!O3q BƌD Nh07֍%4 O5p5܎1B--pq+<Kg?%ߑ)#ImJؒ!&$A.f I&D'#l ݔ6,53bX*o/JʖJ`# -6D${J 1;Vq+ʙ6Le|$Κ%0Ii"›* .:+ULA%?(e"&#؝'!$ F\QR&&(-O(} GǟJ?Z8OӠ# <I2f$̡ ! <]>t8F-3Ga/A٣48P\0-5Gc.+ڥ6D=!¦4>$U.z3@ݧ$>+c2#¨  ,*-WHΩ:9#;]DDު?#c |;(Ŭ 9.'hF"׭"N)l=)Ԯ0./E^JtFdL4AM?:ϱ )Bs[Gϲ@'XM<γa Jmf9$Y6~/818:j<;%'5Mn]2 et!` j & m {   $-c_Iy ?u=;@ T]E }D @t r!yS x saw2a 2w  e`^ tF[v 9 xB  * rRn r v} ( z W T b; {,A Qp7 Vb ) )CK+t?, $v|- lK   nz? ?6RYP`3  Z Iee 0 X I s{ q Sz " 3$%5 u hM  BB 'n]>  + Z *jA `#  f Y Wv M / !k 'U W 8 } "RT b } [N | c @ F$ ^U u s D FXjA ,2e > ? q Of6IF q" be ^t ZW&g ) 67iL6 .G  B" A= F| u x9j > g < ,4M . " UtV # ,t h5 |ph oB l<'  C )\R P&    D;1 <?S k  B jH q 5> mhJ: Zak  fw QH Y *  J yqxd{h0Ok fY -o,)b; 3"NZ' ? P  R pg/  C @ \ CiO a CC W f gn @ } ; V X X_ 1N` : 8Nd l   }U]    G o] -05 EL$  % gN \{ < ~ s  ; //-GJ GD U;O- :b4 :U u|o_ jX vSoA w2Kd7H !  >2 + Jr bZ s yK - Y , " ; + \x Sb 5  =\  ! z M B #rb  8[&   ~ _ &L<a !\k]HM ^{3 j.' {X*N  *= x #(E J.2; yvcx VZ ([ @ @ad : 7 b e F _[ * 0   (  N  ~ & ] ` y - s r GM>O   my<S] ( si. T 4 LD    | X V frIcx1 a . | n TF 7 (8K  c dE  % J8[  $ )Q   Df QO  J9  ?= a  7h%] [ Vz @+a I\ T H K,cw w! _- `  ;i 1S$ - # u < _p ?  w I= 91G j i5A 0] L) I O I L YWm }u+m +M_x4zz4Fh YO s N d,T +/   y* e  0 M \ uV r  q v   N 8Ehw 6?H }\ Z jU \ 9x P'`q Ve c,   ~A| p h  k > .Kp =1(_{ l  n~&m"clrb lg sa  5  pU W1g$4'v %OW&  &1C $n 6 U%M:?o 9 f*D   T h]wZ  . .NeU     iO % `F)>  zYp c Ml 0eJ >6 n ~  8 m6aa 0 pmlC^'&0 h/ og;8F:%Q O ~  4 q}  /RuNym m   @ d t[W 1  R$ r  :yN{ P c jo X {o , L % ]qsgWKt G  +QF Fm k 8.7 zTO +r P~ =c2 KEu D vk~ * "   ^f &. t S  7P g !AZ _  i  S c*T i<&;HQ ! G'7 =d}*l KCJ 4 A ) < S ~v[ w 9 (, X^ ` R I  Ad4#5 ` 9nM>E oL TnC p( f = R  /  7 |3  {K Q l _zED m3  2i d [-# D X# ~ i q ! 4A r } $ #87Y+ 'W"B|   /  6 3PP n  <    S (n 9|Xw ^ p K  L_  Q QJ52  7d/ % x <Q3 kk %  s U V= UPoT( #C^ ^ Ev zf90 ) B H  ' DQA%  6gu h  2  R6 wH:4  @ + !R e @ >i}E  Z # l B ?!V    Y JV l o 1 - q$ 4   69L Y: " tCP0 d J#  Bkb E > =)G:W  L  j\[    p   G H1E 0^Y3 | GV DjI1 ^  [u3 'ZvI  {3s8@R \ 5y 55( 3<  G 9.S  q) * i f: zy    g t8  X/  P2B" H   L M k `/H~x disabling current template maps extending current template maps configuration using current keyword template maps configuration using custom keyword template maps keywords expanded Final summary: The following predicates are supported: Write the introductory message for the patch series. [+] marked option can be specified multiple times additional help topics: aliases: %s broken pipe diffs (%d lines): diffs (truncated from %d to %d lines): keywords written to %s: use "hg -v help %s" to show more info use "hg help %s" to show the full help text use "hg help -c %s" to see help for the %s command hg clone --uncompressed http://server/repo -u 1.5 hg clone -r 04e544 experimental/ good/ hg clone http://selenic.com/hg hg clone project/ project-feature/ hg clone ssh://user@server//home/projects/alpha/ hg export --git -r 123:150 > changes.txt hg export -r "outgoing()" -o "%n-%m.patch" hg export -r 9353 | hg import - hg log -r "bisect(current)" hg log -r "bisect(range)" $ ls foo.c $ hg status ? foo.c $ hg add adding foo.c $ hg status A foo.c $ cp -al REPO REPOCLONE qguard foo.patch -- -stable (negative guard) qguard bar.patch +stable (positive guard) qselect stable # 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 - all changesets that touch a directory, with diffs, excluding merges:: - all revision numbers that match a keyword:: - changesets ancestral to the working directory:: - changesets with full descriptions and file lists:: - check the most recent revision of a remote repository:: - clone a remote repository to a new directory named hg/:: - clone from an absolute path on an ssh server (note double-slash):: - compare a file in the current working directory to its parent:: - create a lightweight local clone:: - export all the changesets between two revisions to a file with rename information:: - find all changesets by some user in a date range:: - last 10 commits on the current branch:: - show changes in the working directory relative to a changeset:: - split outgoing changes into a series of patches with descriptive names:: - summary of all changesets after the last tag:: - use export and import to transplant a bugfix to the current branch:: -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. = ======= == == == == 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 Examples: For efficiency, hardlinks are used for cloning whenever the source and destination are on the same filesystem (note this applies only to the repository data, not to the working directory). Some filesystems, such as AFS, implement hardlinking incorrectly, but do not report errors. In these cases, use the --pull option to avoid hardlinking. 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 listed as A (added) Mercurial will update the working directory to the first applicable revision from this list: See :hg:`help revsets` for more about the `bisect()` keyword. Some examples: 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. 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 tipmost head of the default branch h) tip 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 -o -m mbox && # generate an mbox file... mutt -R -f mbox # ... and view it with mutt hg email -o -m mbox && # generate an mbox file ... formail -s sendmail \ # ... and use formail to send from the mbox -bm -t < mbox # ... using sendmail hg email -r 3000 # send patch 3000 only hg email -r 3000 -r 3001 # send patches 3000 and 3001 hg email -r 3000:3005 # send patches 3000 through 3005 hg email 3000 # send patch 3000 (deprecated) hg qguard other.patch -- +2.6.17 -stable hg qimport -e existing-patch -n new-name include path/to/file-or-dir key parent1, parent2 original_branch_name new_branch_name rename path/to/source path/to/destination s - skip remaining changes to this file f - record remaining changes to this file source author = destination author y - record this change n - skip this change e - edit this change manually hg log -r "not public()" $ hg log -r1 --style changelog $ hg log -r1 --template "{node}\n" b56ce7b07c52de7d5fd79fb89701ea538af65746 %s (Verb) Updating the working directory to a specific changeset. See :hg:`help update`. (deprecated, use configuration file) - 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 - ``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 --branchsort convert from parent to child revision when possible, which means branches are usually converted one after the other. It generates more compact repositories. --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. --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. .. note:: Specifying negative guards now requires '--'. .. note:: 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. .. note:: export may generate unexpected diff output for merge changesets, as it will compare the merge changeset against its first parent only. .. note:: 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:. .. note:: 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. :``%%``: 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 :``%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 :``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.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.saverev: store original revision ID in changeset (forces target IDs to change). It takes a boolean argument and defaults to False. :convert.hg.startrev: convert start revision and its descendants. It takes a hg revision identifier and defaults to 0. :convert.hg.tagsbranch: branch name for tag revisions, defaults to ``default``. :convert.hg.usebranchnames: preserve branch names. The default is True. :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. :hook.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. Accepted destination formats [identifiers]: Accepted source formats [identifiers]: 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. 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 tip -n patch will place tip 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. Before using this command, you will need to enable email in your hgrc. See the [email] section in hgrc(5) for details. Bookmarks are pointers to certain commits that move when committing. Bookmarks are local. They can be renamed, copied and deleted. It is possible to use :hg:`merge NAME` to merge from a given bookmark, and :hg:`update NAME` to update to a given bookmark. Bookmarks can be pushed and pulled between repositories (see :hg:`help push` and :hg:`help pull`). This requires both the local and remote repositories to support bookmarks. For versions prior to 1.8, this means the bookmarks extension must be enabled. 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. 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, 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 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. 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. 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``. Create a copy of an existing repository in a new directory. 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. Elements: Empty lines and lines starting with a ``#`` are ignored. 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 each element in HGRCPATH: For remote repository, using --bundle avoids downloading the changesets twice if the incoming is followed by a pull. 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. 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 -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 changesets without children will be shown. 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 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 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 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 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, or tip if no revision is checked out. If no revision is given, the parent of the working directory is used, or tip if no revision is checked out. If no revision is specified, the working directory's parent is a head revision, and the current branch contains exactly one other head, the other head is merged with by default. Otherwise, an explicit revision with which to merge with must be provided. If no revision range is specified, the default is ``tip:0`` unless --follow is set, in which case the working directory parent is used as the starting revision. If one or more REVs are given, only branch heads on the branches associated with the specified changesets are shown. This means that you can use :hg:`heads foo` to see the heads on a branch named ``foo``. 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 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 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 there are outstanding changes in the working directory, import will abort unless given the -f/--force flag. 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 tipmost head of the current named branch 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 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``. Initialize a new repository in the given directory. If the given directory does not exist, it will be created. 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. 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. Name a particular revision using . 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. 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 latest (tipmost) head 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). Only local paths and ``ssh://`` URLs are supported as destinations. For ``ssh://`` destinations, no working directory or ``.hg/hgrc`` will be created on the remote side. Option -q/--quiet hides untracked (unknown and ignored) files unless explicitly requested with -u/--unknown or -i/--ignored. 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 are the same as for the export command, with the following additions: 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. Please see :hg:`help urls` for important details about ``ssh://`` URLs. If DESTINATION is omitted, a default path will be used. 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. 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, or tip if no revision is checked out. 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. Prints the list of directories being watched by the inotify server. Pull changes from a remote repository to a local one. 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. Repository "heads" are changesets with no child changesets. They are where development generally takes place and are the usual targets for update and merge operations. Branch heads are changesets that have no child changeset on the same branch. Return 0 on success. 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. Returns 0 on success, 1 if an update had unresolved files. Returns 0 on success, 1 if any warnings encountered. Returns 0 on success, 1 if errors are encountered. Returns 0 on success, 1 if no changes found. Returns 0 on success, 1 if no rollback data is available. Returns 0 on success, 1 if nothing changed. Returns 0 on success, 1 if nothing to rebase. Returns 0 on success, 1 if there are unresolved files. 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 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 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. 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 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. 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. Specifying a path to a repository root or Mercurial bundle will cause lookup to operate on that repository/bundle. Statistics are based on the number of changed lines, or alternatively the number of matching revisions if the --changesets option is specified. Such a file may be specified with the --aliases option, otherwise a .hgchurn file will be looked for in the working directory root. Supports switching between different patch queues, as well as creating new patch queues and deleting existing ones. 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 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, and the exclusion of all other files and directories not explicitly 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 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 (eg: 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 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 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 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 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 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, 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 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 will display a histogram representing the number of changed lines or revisions, grouped according to the given template. The default template will group changes by author. The --dateformat option may be used to group the results by date instead. This finds all changes from the repository at the specified path or URL and adds them to a local repository (the current one unless -R is specified). By default, this does not update the copy of the project in the working directory. This finds all changes from the repository at the specified path or URL and adds them to the local repository. This 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: This operation is symmetrical to pull: it is identical to a pull in the destination repository from the current one. 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 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 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 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 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 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. 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, branch will not let you set a branch name that already exists, even if it's inactive. 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 --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 --to-normal to convert largefiles back to normal files; after this, the DEST repository can be used without largefiles at all. Use -C/--clean to reset the working directory branch to that of the parent of the working directory, negating a previous branch change. Use -d/--default to disable current configuration. Use -f/--force to override the default behavior and push all changesets on all branches. 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 :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. 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 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. With --debug, the source (filename and line number) is printed for each config item. 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 -i/--inactive, the new bookmark will not be made the active bookmark. If -r/--rev is given, the new bookmark will not be made active even if -i/--inactive is not given. If no NAME is given, the current active bookmark will be marked inactive. 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 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 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 repository branch heads. 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 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 -c/--confirm options, you will be presented with a final summary of all messages and asked for confirmation before the messages are sent. Without argument, pops off the top of the patch stack. If given a patch name, keeps popping off patches until the named patch is at the top of the stack. Without the -a/--text option, annotate will avoid processing files it detects as binary. With -a, annotate will annotate the file anyway, although the results will probably be neither useful nor desirable. Without the -a/--text option, diff will avoid generating diffs of files it detects as binary. With -a, diff will generate a diff anyway, probably with undesirable results. Without the -a/--text option, export will avoid generating diffs of files it detects as binary. With -a, export will generate a diff anyway, probably with undesirable results. You can change 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 register an existing patch inside the patch directory with the -e/--existing flag. 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 :hg:`bookmark NAME` to set a bookmark on the working directory's parent revision with the given name. If you specify a revision using -r REV (where REV may be an existing bookmark), the bookmark is assigned to that revision. 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:: [bugzilla] bzurl=http://my-project.org/bugzilla user=bugmail@my-project.org password=plugh version=xmlrpc bzemail=bugzilla@my-project.org 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 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 [extensions] bugzilla = [hooks] # run bugzilla hook on every change pulled or pushed in here incoming.bugzilla = python:hgext.bugzilla.hook [keyword] # expand keywords in every python file except those matching "x*" **.py = x* = ignore [keywordset] # prefer svn- over cvs-like default keywordmaps svn = True [usermap] user@emaildomain.com=user.name@bugzilladomain.com [web] baseurl=http://my-project.org/hg aliases: %s committer = Bugzilla user 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. kwexpand refuses to run if given files contain local changes. kwshrink refuses to run if given files contain local changes. 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 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 tip --template "{date|isodate}\n" 2008-08-21 18:22 +0000 # 'none' turns off all effects status.clean = none status.copied = none # 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 # 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 # 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 # user6 will not have write access to any file: ** = user6 $ 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 $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. %s in %s should not have %s line endings -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 :``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}`` See also the ``[usermap]`` section. [acl.allow.branches] [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] # 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 [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, eg # 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 [diff-tools] kdiff3.diffargs=--L1 '$plabel1' --L2 '$clabel' $parent $child [email] from = My Name to = recipient1, recipient2, ... cc = cc1, cc2, ... bcc = bcc1, bcc2, ... reply-to = address1, address2, ... [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] # 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 [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 [interhg] issues = s!issue(\d+)!issue\1! bugzilla = s!((?:bug|b=|(?=#?\d{4,}))(?:\s*#?)(\d+))!\1!i boldify = s!(^|\s)#(\d+)\b! #\2! [largefiles] minsize = 2 [largefiles] patterns = *.jpg re:.*\.(png|bmp)$ library.zip content/audio/* [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] ignore = version, help, update [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 glob pattern, value is a comma-separated list of subscriber # emails pattern = user@host [schemes] py = http://code.python.org/hg/ [ui] username = Firstname Lastname verbose = True [web] # If you want hyperlinks (optional) baseurl = http://server/path/to/repo [web] pygments_style =