6hܖ (SrSSKJr SSKrSSKrSSKrSSKrSSKrSSKrSSK J r SSK J r J r Jr SSKJr SSKJrJrJrJrJrJrJrJrJrJrJrJrJ r J!r!J"r"J#r# Sr$0r%\RL"\%5r&0r'\RP"\'5r(SSSSS S S S .r)\)RU5Hur+r,\("S S \+-\,S S9 M \("S SSS9 \("S SSS9 \("S S\-S9 S=Sjr.SSS \ "S54r/SS/\ "S5\ "S54r0SS/\ "S5\ "S54r1SS /\ "S!5\ "S54r2S"S#S \ "S$54r3SS%S \ "S&54r4\ "S'5r5\&"S \/\0\1\2\3\4/\5\&RlS(9S)5r7S*r8S+r9S,r:S-r;S.rS1r?S2r@S3rAS4rBS5rCS6rDS7rES8rFS9rGS:rH"S;S<5rIg)>arewrite file content in changesets or working copy (EXPERIMENTAL) Provides a command that runs configured tools on the contents of modified files, writing back any fixes to the working copy or replacing changesets. Fixer tools are run in the repository's root directory. This allows them to read configuration files from the working copy, or even write to the working copy. The working copy is not updated to match the revision being fixed. In fact, several revisions may be fixed in parallel. Writes to the working copy are not amended into the revision being fixed; fixer tools MUST always read content to be fixed from stdin, and write fixed file content back to stdout. Here is an example configuration that causes :hg:`fix` to apply automatic formatting fixes to modified lines in C++ code:: [fix] clang-format:command=clang-format --assume-filename={rootpath} clang-format:linerange=--lines={first}:{last} clang-format:pattern=set:**.cpp or **.hpp The :command suboption forms the first part of the shell command that will be used to fix a file. The content of the file is passed on standard input, and the fixed file content is expected on standard output. Any output on standard error will be displayed as a warning. If the exit status is not zero, the file will not be affected. A placeholder warning is displayed if there is a non-zero exit status but no standard error output. Some values may be substituted into the command:: {rootpath} The path of the file being fixed, relative to the repo root {basename} The name of the file being fixed, without the directory path If the :linerange suboption is set, the tool will only be run if there are changed lines in a file. The value of this suboption is appended to the shell command once for every range of changed lines in the file. Some values may be substituted into the command:: {first} The 1-based line number of the first line in the modified range {last} The 1-based line number of the last line in the modified range Deleted sections of a file will be ignored by :linerange, because there is no corresponding line range in the version being fixed. By default, tools that set :linerange will only be executed if there is at least one changed line range. This is meant to prevent accidents like running a code formatter in such a way that it unexpectedly reformats the whole file. If such a tool needs to operate on unchanged files, it should set the :skipclean suboption to false. The :pattern suboption determines which files will be passed through each configured tool. See :hg:`help patterns` for possible values. However, all patterns are relative to the repo root, even if that text says they are relative to the current working directory. If there are file arguments to :hg:`fix`, the intersection of these patterns is used. There is also a configurable limit for the maximum size of file that will be processed by :hg:`fix`:: [fix] maxfilesize = 2MB Normally, execution of configured tools will continue after a failure (indicated by a non-zero exit status). It can also be configured to abort after the first such failure, so that no files will be affected if any tool fails. This abort will also cause :hg:`fix` to exit with a non-zero status:: [fix] failure = abort When multiple tools are configured to affect a file, they execute in an order defined by the :priority suboption. The priority suboption has a default value of zero for each tool. Tools are executed in order of descending priority. The execution order of tools with equal priority is unspecified. For example, you could use the 'sort' and 'head' utilities to keep only the 10 smallest numbers in a text file by ensuring that 'sort' runs before 'head':: [fix] sort:command = sort -n head:command = head -n 10 sort:pattern = numbers.txt head:pattern = numbers.txt sort:priority = 2 head:priority = 1 To account for changes made by each tool, the line numbers used for incremental formatting are recomputed before executing the next tool. So, each tool may see different values for the arguments added by the :linerange suboption. Each fixer tool is allowed to return some metadata in addition to the fixed file content. The metadata must be placed before the file content on stdout, separated from the file content by a zero byte. The metadata is parsed as a JSON value (so, it should be UTF-8 encoded and contain no zero bytes). A fixer tool is expected to produce this metadata encoding if and only if the :metadata suboption is true:: [fix] tool:command = tool --prepend-json-metadata tool:metadata = true The metadata values are passed to hooks, which can be used to print summaries or perform other post-fixing work. The supported hooks are:: "postfixfile" Run once for each file in each revision where any fixer tools made changes to the file content. Provides "$HG_REV" and "$HG_PATH" to identify the file, and "$HG_METADATA" with a map of fixer names to metadata values from fixer tools that affected the file. Fixer tools that didn't affect the file have a value of None. Only fixer tools that executed are present in the metadata. "postfix" Run once after all files and revisions have been handled. Provides "$HG_REPLACEMENTS" with information about what revisions were created and made obsolete. Provides a boolean "$HG_WDIRWRITTEN" to indicate whether any files in the working copy were updated. Provides a list "$HG_METADATA" mapping fixer tool names to lists of metadata values returned from executions that modified a file. This aggregates the same metadata previously passed to the "postfixfile" hook. You can specify a list of directories to search the tool command in using the `fix.extra-bin-paths` configuration. ) annotationsN)_)nullidnullrevwdirrev)procutil)cmdutilcontextcopiesencodingerror logcmdutilmatchmdiffmerge mergestatepycompat registrar rewriteutilscmutilutilworkersships-with-hg-coreFT)scommands linerangespatternsprioritymetadatas skipcleansenabledfixs.*:%s$)defaultgeneric maxfilesizes2MB)rfailurecontinueextra-bin-pathscURSS5nUS;a+[R"[S5U4-[S5S9eUS:Xa[R"XS9eg) z)Abort with 'message' if fix.failure=abortrr)rabortsunknown fix.failure action: %ssuse "continue" or "abort"hintr"N)configr Abortr)uimessager$actions +/usr/lib/python3/dist-packages/hgext/fix.pychecktoolfailureactionr+sc YYvz *F ,,kk / 0F9 </0  kk'--r,alls)fix all non-public non-obsolete revisionsbasesdrevisions to diff against (overrides automatic selection, and applies to every revision being fixed)sREVrrevsrevisions to fix (ADVANCED)ssources1fix the specified revisions and their descendantsws working-dirsfix the working directorywholesalways fix every line of a files[OPTION]... [FILE]...) helpcategoryc \^^^^^^[R"T5m[R"TSSS5 [R"TSSS/5 TR 5 TR 5 TRS5 [TTT5n[TTU5m[TTUTUT5upV[TTUT5m[T5m[TUT5 UUUUUU4Sjn[R"TSU[5USS 9n[ R""[$5n [ R""[&5n 0n Sn [)US S 9n TR+[-S 5[-S 5[/UR155S9nUGH unnnnUR3US9 UR55HunnU UR7U5 M Ub6UXU'UUUS.nTR8"SSS0[R:"U5D6 Xo==S-ss'U (dMXmS(aMU R=5nTUnU[>:Xa[ATUXU 5 [CX5n O[ETTUXU 5 X U (dMXmS(dMgGM SSS5 [GTX5 U U U S.nTR8"SSS 0[R:"U5D6 SSS5 SSS5 SSS5 g!,(df  Na=f!,(df  N0=f!,(df  N9=f!,(df  g=f)arewrite file content in changesets or working directory Runs any configured tools to fix the content of files. (See :hg:`help -e fix` for details about configuring tools.) Only affects files with changes, unless file arguments are provided. Only affects changed lines of files, unless the --whole flag is used. Some tools may always affect the whole file regardless of --whole. If --working-dir is used, files with uncommitted changes in the working copy will be fixed. Note that no backup are made. If revisions are specified with --source, those revisions and their descendants will be checked, and they may be replaced with new revisions that have fixed file content. By automatically including the descendants, no merging, rebasing, or evolution will be required. If an ancestor of the working copy is included, then the working copy itself will also be fixed, and the working copy will be updated to the fixed parent. When determining what lines of each file to fix at each revision, the whole set of revisions being fixed is considered, so that fixes to earlier revisions are not forgotten in later ones. The --base flag can be used to override this default behavior, though it is not usually desirable to do so. r-r2r0 working_dirrc 3># UHLupnTUnXBR5n[TTT T UUT T U5upgXu:waUOSnUH n XXh4v M MN g7fN)datafixfile)itemssrcrevpathdstrevsctxolddatametadatanewdatar:dstrevbasectxs basepathsfixersoptsrepor's r*getfixesfix..getfixes%sy).%g6l)..*$+V$ %!"#*"4w$%F!88&+*/sAAg?F) threadsafeT)reversesfixingsfiles)topicunittotalitemN)r0spathrthrow)s replacementss wdirwrittenr)s postfixfile)spostfix)$r byteskwargsr check_at_most_one_argcheck_incompatible_argumentswlocklock transaction getrevstofix getbasectxs getworkqueue getbasepaths getfixers_prefetchfilesrtuple collections defaultdictdictlistsorted makeprogressrsumvalues incrementr<appendhook strkwargspoprwriteworkingdirbool replacerevcleanup)r'rIpatsrH revstofix workqueuenumitemsrJresultsfiledataaggregatemetadata replacements wdirwritten commitorderprogressrevr>filerevmetadatarC fixername fixermetadatahookargsr@rErFrGs`` ` @@@r*fixrs<    %D !!$ 6B (( nvy1 tyy{D$4$4V$< T40 tT95* dD)X  !tYA 2 tY 2 9 92-- Xuw e **40'33D9  Y5 __I,Qx[HOO3T?G"""-0?0E0E0G,I}%i077 F1H&*1HM$' #!%%4 H II&##,,X6  " "k(r?*C*C%//+Cs)Cg~'c8=,O&*8=&9 "2tS(-N "k(r?*C*C+8? D l0)'*  IDIH,>,>x,HIA%={p  q%=$<{{sp L1L C;K;>BK*  K* #AK* < K* K* AK;L L* K8 4K;; L L  L L L+cUR5VVs0sHup4X4/_M nnn[R"XSSS9 gs snnf)aCalls scmutil.cleanupnodes() with the given replacements. "replacements" is a dict from nodeid to nodeid, with one key and one value for every revision that was affected by fixing. This is slightly different from cleanupnodes(). "wdirwritten" is a bool which tells whether the working copy was affected by fixing, since it has no entry in "replacements". Useful as a hook point for extending "hg fix" with output summarizing the effects of the command, though we choose not to output anything here. rT)fixphaseN)r<r cleanupnodes)rIr{r|precsuccs r*rsrsxsB4@3E3E3GH3GZTD&L3GLH VdCIs=c "[R"[5n[R"[5nUR SS5n[ U5Hn Xn [ R"XU5n [ [XX#XU U 55Hn Xn U R5(aMU R5U:a5UR[S5[R"U5U 4-5 Mg[SXY55nXmR!5X4R#U 5 Xy==S- ss'M M UR%5VVV Vs/sHuunnn n['U5U U4PM nn nnnUR)5 UU4$s snn nnf)aConstructs a list of files to fix and which revisions each fix applies to To avoid duplicating work, there is usually only one work item for each file revision that might need to be fixed. There can be multiple work items per file revision if the same file needs to be fixed in multiple changesets with different baserevs. Each work item also contains a list of changesets where the file's data should be replaced with the fixed data. The work items for earlier changesets come earlier in the work queue, to improve pipelining by allowing the first changeset to be replaced while fixes are still being computed for later changesets. Also returned is a map from changesets to the count of work items that might affect each changeset. This is used later to count when all of a changeset's work items have been finished, without having to inspect the remaining work queue in each worker subprocess. The example work item (1, "foo/bar.txt", (1, 2, 3)) means that the data of bar.txt should be read from revision 1, then fixed, and written back to revisions 1, 2 and 3. Revision 1 is called the "srcrev" and the list of revisions is called the "dstrevs". In practice the srcrev is always one of the dstrevs, and we make that choice when constructing the work item so that the choice can't be made inconsistently later on. The dstrevs should all have the same file revision for the given path, so the choice of srcrev is arbitrary. The wdirrev can be a dstrev and a srcrev. rrs!ignoring file larger than %s: %s c3@# UHoR5v M g7fr9)r).0r@s r* getworkqueue..s@-3WWYY-srT)rcrdrfint configbytesrgrr pathstofixislinksizewarnrr bytecountrbfilerevrlr<minsort)r'rIrtrHrurE dstrevmaprw maxfilesizerfixctxrr>fctxbaserevs_filerev _baserevsr?rvs r*r^r^sf4''-I&&s+H..8Ki  fD1 rUSM6 J D >s C MQ M !(5>OO4E4E 0 'Xy$ WtW%4ENN h sF cRUS(aURS5nOUS(a[R"XS5n[URSU55n[U;aUR [5 USR 5U;aUR [5 OM[[R"XS55nURS5(aUR [5 [U5S:Xa [U;d-[R"U5 [R"XS 5 [U;aG[RRU5R!5(a["R$"S S S 9eU(d["R$"S SS 9eU$)z8Returns the set of revision numbers that should be fixedr-s+(not public() and not obsolete()) or wdir()r2s(%ld::) - obsolete().r0r7rTrsunresolved conflictssuse 'hg resolve'r#sno changesets specifiedsuse --source or --working-dir)revsrrevrangesetraddrgetlenr checkunfinishedrprecheck mergestatemodrreadunresolvedcountr r&)r'rIrHr source_revss r*r\r\s; F|yyGH i ))$Y@ 4994kBC k ! HHW  :>> t # HHW :&&t&\:; 88N # # HHW  INw$%T04  $ $ ) )$ / ? ? A Akk18KLL kk &-M   Kr,c $[5nUHnURXd[U5[U5S9n UR[[R "U R U RU RU R555 M U$)zReturns the set of files that should be fixed in a context The result depends on the base contexts; we include any file that has changed relative to any of the base contexts. Base contexts should be ancestors of the context being fixed. )r listclean listunknown) rstatusrqupdate itertoolschainaddedmodifiedcleanunknown) r'rIrtrHrrErfilesbasectxstats r*rrsy EE~~ 4:4:   JJ tzz4<<   Lr,c<URS5(a [SU5$/nUHhnURUR5UR5U4U5nX;aXxR5n OSn UR [X55 Mj [ U5$)aReturns the set of line ranges that should be fixed in a file Of the form [(10, 20), (30, 40)]. This depends on the given base contexts; we must consider lines that have changed versus any of the base contexts, and whether the file has been renamed versus any of them. Another way to understand this is that we exclude line ranges that are common to the file in all base contexts. r4r,)rdifflinerangesrr:extend unionranges) rHr>rFrErcontent2 rangeslistrbasepathcontent1s r* linerangesrs xxc8,,J=='++-t!DdK  (--/HH.<= z ""r,cURS5(a0$0nUHdupVnXnX5HRn [R"X5RXf5n X;dM/XU R5UR5U4'MT Mf U$)Nr4)rr pathcopiesr) rIrHrvrErFr=r>_dstrevsrrrs r*r_r_s xx I"+h'G((9==dIH"AI7;;=&**,=>(#, r,c[[U55n/nU(a US/USSpUH8up#USupEX%S-:aURX#45 M(U[X554US'M: U$)aReturn the union of some closed intervals >>> unionranges([]) [] >>> unionranges([(1, 100)]) [(1, 100)] >>> unionranges([(1, 100), (1, 100)]) [(1, 100)] >>> unionranges([(1, 100), (2, 100)]) [(1, 100)] >>> unionranges([(1, 99), (1, 100)]) [(1, 100)] >>> unionranges([(1, 100), (40, 60)]) [(1, 100)] >>> unionranges([(1, 49), (50, 100)]) [(1, 100)] >>> unionranges([(1, 48), (50, 100)]) [(1, 48), (50, 100)] >>> unionranges([(1, 2), (3, 4), (5, 6)]) [(1, 6)] rrTNrU)rgrrlmax)runionedabcds r*rr)ss,J(JG)!}oz!"~r{ 1u9 NNA6 "c!i.GBK  Nr,c/n[R"X5H1up4USSupVUS:XdMXV:wdMURUS-U45 M3 U$)aNReturn list of line number ranges in content2 that differ from content1. Line numbers are 1-based. The numbers are the first and last line contained in the range. Single-line ranges have the same line number for the first and last line. Excludes any empty ranges that result from lines that are only present in content1. Relies on mdiff's idea of where the line endings are in the string. >>> from mercurial import pycompat >>> lines = lambda s: b'\n'.join([c for c in pycompat.iterbytestr(s)]) >>> difflineranges2 = lambda a, b: difflineranges(lines(a), lines(b)) >>> difflineranges2(b'', b'') [] >>> difflineranges2(b'a', b'') [] >>> difflineranges2(b'', b'A') [(1, 1)] >>> difflineranges2(b'a', b'a') [] >>> difflineranges2(b'a', b'A') [(1, 1)] >>> difflineranges2(b'ab', b'') [] >>> difflineranges2(b'', b'AB') [(1, 2)] >>> difflineranges2(b'abc', b'ac') [] >>> difflineranges2(b'ab', b'aCb') [(2, 2)] >>> difflineranges2(b'abc', b'aBc') [(2, 2)] >>> difflineranges2(b'ab', b'AB') [(1, 2)] >>> difflineranges2(b'abcde', b'aBcDe') [(2, 2), (4, 4)] >>> difflineranges2(b'abcde', b'aBCDe') [(2, 4)] !rT)r allblocksrl)rrrangeslineskind firstlinelastlines r*rrLsUNFx: #Aaj 4rbaserevfixrevrrs r*rarasJ#,h W  ~&#, .7__->)$*+.? ", !+ICg((v67!+   s%B/ c[R(a[RR 5nUR SS5nUVs/sHo@R U5PM nnXR[R5-n[RR U5US'U$[R"5=(d [R"5nUVs/sHowRUS5PM nnURRUS5n UVs/sH"n[RR X5PM$ nn[RR 5nUR SS5nXR[R 5-n[R R U5US'U$s snfs snfs snf)NsPATHr,ignorePATH)ossupports_bytes_environr environcopyrjoinsplitr ospathsepsysgetfilesystemencodinggetdefaultencodingdecodebaser>pathsep) wvfs extra_pathsenvraw_pathi path_items path_encodingp extra_strrs r*_augmented_envrsW   ##%777C(-89[yy|[ 9 >>(2D2D#EE ))..z:G  J113Os7M7M7O @KL 1XXmX6 Lyy x84=>IqRWW\\$*I >ll!7762& !== ll'' 3F J: M>s F= G)Gc 0nXER5n Sn URSS5n U (a[URU 5n UR 5GHupU R X$U5(dM[ X%XgXI5nU RXU5nUcMCSnUXLU4-nURU5 URSU4-5 [R"[R"U5S[R"UR5[R[R[RU S9nURU 5unnU(a[!XR#5U U5 UnU R%5(a/UR'SS 5unn[(R*"U5X'OSX'UR2S :XaUn GM}U(d4[1S 5UR24-n[!XR#5U U5 [5U[1S 5[1S5S9 GM X4$![,a# UR/[1S 5U 4-5 GM f=f)a Run any configured fixers that should affect the file in this context Returns the file content that results from applying the fixers in some order starting with the file's content in the fixctx. Fixers that support line ranges will affect lines that have changed relative to any of the basectxs (i.e. they will only avoid lines that are common to all basectxs). A fixer tool's stdout will become the file's new content if and only if it exits with code zero. The fixer tool's working directory is the repository's root. Nrr sfixing: %s - %s - %s ssubprocess: %s T)shellcwdstdinstdoutstderrrrTs+ignored invalid output from fixer tool: %s rsexited with status %d sno fixes will be appliedsFuse --config fix.failure=continue to apply any successful fixes anywayr#)r: configlistrrr<affectsrcommanddebug subprocessPopenr tonativestrrootPIPE communicate showstderrrshouldoutputmetadatarr json_loads ValueErrorrr returncoder+)r'rIrHrGrr>rFrErBrCrrrfixerrrmsgprocrr newerdata metadatajsonr(s r*r;r;s%Hl!G C--(:;KTYY 4"LLN ==t , ,IFmmBf5G+C Ft, ,C HHSM HH(G:5 6##$$W-((3 oo!!D"--g6NFF2zz|Y?I))++.4ll5!.D+L)*2*=*=l*KH''+#!## :;t>PPGr::<GD&123W+f  -"GGIJ$,' s -H33(I I c[R"SU5HbnU(dM URS5 UcUR[S5SS9 OURSU-SS9 URSX$4-5 Md g) a%Writes the lines of the stderr string as warnings on the ui Uses the revision number and fixername to give more context to each line of the error message. Doesn't include file names, since those take up a lot of space and would tend to be included in the error message if they were relevant. s[ ]+[Nswdirs evolve.rev)labels%ds ] %s: %s )rerrr)r'rrrlines r*rrsjV, 4 GGDM{' -8 =9 GGMY$55 6-r,cUR5H(upEXnURXVR55 M* URR 5nUR Xw5nX:wabURR 5[:XdeURRU5 [R"XU5 SSS5 gg!,(df  g=f)aWrite new content to the working copy and check out the new p1 if any We check out a new revision if and only if we fixed something in both the working directory and its parent revision. This avoids the need for a full update/merge, and means that the working directory simply isn't affected unless the --working-dir flag is given. Directly updates the dirstate for the affected files. N) r<writeflagsdirstatep1rp2rchanging_parentsr movedirstate) rIr@ryr{r>r:roldp1newp1s r*rprp!snn& y 4&' MM   E   U *E ~}}!V+++ ]] + +D 1  E{ 32 1 1 1s ,C Cc JURRUR55upVXXpURUR 5UR 55n URUR 5UR 55n U(d)UR 5U;aUR 5U;agUR 5R 5n UR5U S'[R"U5n U RX5 [R"X,S9 [R"XUR55 UR!5HRn X-nUR#5nU R%XU UR'5S9 U(dMAU R)X5 MT [*R,"UUR/5UR15VVs0sH unnUU/_M snn5nU R3UUR55U UR75X4UR95S9nUR;5nUR 5nUU:Xa#UR=SUR5-5 gUXBR 5'gs snnf)awCommit a new revision like the given one, but with file content changes "ctx" is the original revision to be replaced by a modified one. "filedata" is a dict that maps paths to their new file content. All other paths will be recreated from the original revision without changes. "filedata" may contain paths that didn't exist in the original revision; they will be added. "replacements" is a dict that maps a single node to a single node, and it is updated to indicate the original revision is replaced by the newly created one. No entry is added if the replacement's node already exists. The new revision has the same parents as the old one, unless those parents have already been replaced, in which case those replacements are the parents of this new revision. Thus, if revisions are replaced in topological order, there is no need to rebase them into the original topology later. Ns fix_source)wc)r)textbranchextradaterusersnode %s already existed ) changelog parentrevsrrnoder+rhexr overlayworkingctxsetbaser revert_tor graftcopiesr!keys copysourcerr markcopiedrupdate_hash_refs descriptionr<tomemctxr*r,r-commitr)r'rIr@ryr{p1revp2revp1ctxp2ctx newp1node newp2noder+wctxr>rr7oldnodenewnodedescmemctxsucnodeprenodes r*rrrr7s (>>,,SWWY7LE; 5  uzz|getfixers..sQ0A0Ar,T)keyrM) fixernames configboolr% configintrrrFixerrc OrderedDictrgr<) r'rGnameenabledrpattern linerangepriorityrB skipcleans r*r`r`sD F2--{(:;))FD;$67))FD;$67IIfd]&:; <<|(;<== )<=MM&$*>? ? GGBCtgM _ GGBCtgM  HH:dWD E )xFL/4  " "v||~#A4P r,c[5nURS5H1up#SU;dM URURSS5S5 M3 U$)z>Returns the names of [fix] config options that have suboptionsr:rTr)r configitemsrr)r'nameskvs r*rPrPsH EEv& 19 IIaggdA&q) *' Lr,c0\rSrSrSrSrSrSrSrSr g) rSiz4Wraps the raw config values for a fixer with methodscLXlX lX0lX@lXPlX`lgr9)_command_pattern _linerangerL _metadata _skipclean)selfrrWrXrYrBrZs r*__init__Fixer.__init__s"  #!!#r,cUR5n[R"URURUR/US9nU"U5$)z@Should this fixer run on the file at the given path and context?)r@)rImatchmodrr rd)rhrHrr>rImatchers r*r Fixer.affectss>{{}.. IItyy4==/v t}r,cUR$)z@Should the stdout of this fixer start with JSON and a null byte?)rf)rhs r*rFixer.shouldoutputmetadatas ~~r,c `[RnU"UURU[RR U5S.5/nUR (aHUR(aU(dgUH)upgURU"XR XgS.55 M+ SRU5$)zA shell command to use to invoke this fixer on the given file/lines May return None if there is no appropriate command to run for the given parameters. )srootpathsbasenameN)sfirstslast ) r rendercommandtemplatercrr>basenamerergrlr)rhr'r>rexpandpartsfirstlasts r*r Fixer.commands ..  "1A1A$1GH   ??v%  OO-M & yyr,)rcrerfrdrLrgN) __name__ __module__ __qualname____firstlineno____doc__rirrr__static_attributes__r,r*rSrSs>$ r,rSr9)Jr~ __future__rrcrrrrrmercurial.i18nrmercurial.noderrrmercurial.utilsr mercurialr r r r r rrrlrrrrrrrrrr testedwithcmdtabler configtable configitem FIXER_ATTRSr<rOrrfr+alloptbaseoptrevopt sourceoptwdiroptwholeoptusageCATEGORY_FILE_CONTENTSrrsr^r\rrr_rrr]rarr;rrprrr`rPrSrr,r*rsIwr#   %.#    H %  ! !+ .   %%'LCvy3F(  6>62  6:{3 6%t4 . vua LM N   fI  A<=qy I :;fI    *F(G H 5!$F"G H "#   Wfi(; //  ~J  ~JBD";|@,#:  F,^< .,FR7$4,I+X#L1 1 r,