6h/SrSSKJr SSKJr SSKJrJrJrJ r J r J r J r JrJrJr Sr0r\R&"\5rSrSrSrS rS rS r\"S S S/\"S5\"S54SS/\"S5\"S54SS/\"S5\"S54SSS\"S54SS/\"S5\"S54SS/\"S5\"S54SS /\"S!5\"S54SS"S\"S#54SS$S\"S%54SS&S\"S'54/ \R4-\"S(5S)S*9S+5rg,)-aG allow sparse checkouts of the working directory (EXPERIMENTAL) (This extension is not yet protected by backwards compatibility guarantees. Any aspect may break in future releases until this notice is removed.) This extension allows the working directory to only consist of a subset of files for the revision. This allows specific files or directories to be explicitly included or excluded. Many repository operations have performance proportional to the number of files in the working directory. So only realizing a subset of files in the working directory can improve performance. Sparse Config Files ------------------- The set of files that are part of a sparse checkout are defined by a sparse config file. The file defines 3 things: includes (files to include in the sparse checkout), excludes (files to exclude from the sparse checkout), and profiles (links to other config files). The file format is newline delimited. Empty lines and lines beginning with ``#`` are ignored. Lines beginning with ``%include `` denote another sparse config file to include. e.g. ``%include tests.sparse``. The filename is relative to the repository root. The special lines ``[include]`` and ``[exclude]`` denote the section for includes and excludes that follow, respectively. It is illegal to have ``[include]`` after ``[exclude]``. Non-special lines resemble file patterns to be added to either includes or excludes. The syntax of these lines is documented by :hg:`help patterns`. Patterns are interpreted as ``glob:`` by default and match against the root of the repository. Exclusion patterns take precedence over inclusion patterns. So even if a file is explicitly included, an ``[exclude]`` entry can remove it. For example, say you have a repository with 3 directories, ``frontend/``, ``backend/``, and ``tools/``. ``frontend/`` and ``backend/`` correspond to different projects and it is uncommon for someone working on one to need the files for the other. But ``tools/`` contains files shared between both projects. Your sparse config files may resemble:: # frontend.sparse frontend/** tools/** # backend.sparse backend/** tools/** Say the backend grows in size. Or there's a directory with thousands of files you wish to exclude. You can modify the profile to exclude certain files:: [include] backend/** tools/** [exclude] tools/tests/** ) annotations)_) cmdutilcommandserror extensions logcmdutilmergepycompat registrarsparseutilsships-with-hg-corec\S[l[U5 [U5 [ U5 g)NT)r enabled _setupclone _setuplog _setupadd)uis ./usr/lib/python3/dist-packages/hgext/sparse.pyextsetuprdsFNO bM bMcUn[U5(deU[LaKXR;a"URUn[XU"U55 OURSnU[LaMKU[La[ [ S5X14-5eg)zeReplace a filecache property with a new class. This allows changing the cache invalidation condition.rstype '%s' has no property '%s'N)callableobject__dict__setattr __bases__AttributeErrorr)clspropname replacementorigclsorigs rreplacefilecacher$lsG K  V  || #<<)D C;t#4 5 mmA V  f} / 0G3F F  rc[RSnUSRS5 Sn[R"[ SU5 g)Ns log|history)rsparseNs1limit to changesets affecting the sparse checkoutc^^U"TU5nURRS5(a.[R"T5mUU4SjnUR U5nU$)Nr'cT>TUn[U4SjUR555$)Nc3F># UHnT"U5(dMUv M g7f)N).0f sparsematchs r D_setuplog.._initialrevs..ctxmatch..sDk[^11ks! !)anyfiles)revctxrepor.s rctxmatch1_setuplog.._initialrevs..ctxmatchs#3iDciikDDDr)optsgetr matcherfilter)r#r5woptsrevsr6r.s ` @r _initialrevs_setuplog.._initialrevssKD%  ::>>) $ $ ...K E;;x(D rr>)rtableappendr wrapfunctionr )rentryr>s rrr~s> NN> *E !HOO  J Erc(^^^ URS5m URS5mURS5mURS5nU(d9T (dT(dT(a$UUU 4Sjn[R"[SU5 U"X/UQ70UD6$)Nincludeexcludeenable_profilenarrowc >[R"UR5R50TTTSS9 U"U/UQ70UD6$)NT)rErF enableprofileusereporootpaths)r updateconfigr5 unfiltered)r#r4argskwargsrJrFrEs r clonesparse$_clonesparsecmd..clonesparsesI    %%'+!%  -d-f- -rupdate)r9rrBmergemod) r#rr5rNr8 narrow_patrPrJrFrEs @@@r_clonesparsecmdrUsuhhy!Ghhy!GHH-.M(#J 7g . (K@  (4 (4 ((rc[RSnUSRSS/S45 USRSS/S45 USRSS/S 45 [R"[RS[ 5 g) Nscloner&renable-profilesenable a sparse profileincludesinclude sparse patternexcludesexclude sparse pattern)rr@rAr wrapcommandrU)rrCs rrrsu NN8 $E !HOOS+R1KLM !HOOS*b*CDE !HOOS*b*CDE8>>8_Erc[RSnUSRS5 Sn[R"[RSU5 g)Nsaddr&)sr'Ns8also include directories of added files in sparse configcURS5(aZ[5nUH,n[R"U5upxUR U5 M. [ R "X$[U5S9 U"X/UQ70UD6$)Nr )rE)r9setrsplitaddr rLlist) r#rr5patsr8dirspatdirnamebasenames r_add_setupadd.._addsi 88H  5D$(JJsO!!   DJ ?B,t,t,,r)rr@rArrZ)rrCrgs rrrsB NN6 "E !HOO -8>>648rs debugsparseIrXs$include files in the sparse checkoutsPATTERNXrYs$exclude files in the sparse checkoutddeletesdelete an include/exclude rulefforceFs.allow changing rules even with pending changesrrWsenables the specified profilesdisable-profilesdisables the specified profiles import-rulessimports rules from a files clear-ruless"clears local include/exclude rulesrefreshs,updates the working after sparseness changesresetsmakes the repo full agains [--OPTION]T) helpbasicc L[R"U5nURS5nURS5nURS5nURS5nURS5nURS5nURS5n URS5n URS 5n URS 5n [R"USSS 5n [ U=(d& U=(d U =(d U =(d U=(d U5n[ U[ U 5/5nUS :a[R"[S 55eS Ul US:XaURRS5(aURURRS5S-5 [R "U5nU(a=UR[S55 UR#SR%U5S-5 g[R"[S55eU(a[R&"UUUUU U UUUS9 U(a[R("XXS9 U (a[R*"XS9 U (aUR-5 [R."[0[R2"XR5[R4"U5US95n[R6"UUUSUS USS9 SSS5 U? gU? g!,(df  U? g=f)amake the current checkout sparse, or edit the existing checkout The sparse command is used to make the current checkout sparse. This means files that don't meet the sparse condition will not be written to disk, or show up in any working copy operations. It does not affect files in history in any way. Passing no arguments prints the currently applied sparse rules. --include and --exclude are used to add and remove files from the sparse checkout. The effects of adding an include or exclude rule are applied immediately. If applying the new rule would cause a file with pending changes to be added or removed, the command will fail. Pass --force to force a rule change even with pending changes (the changes on disk will be preserved). --delete removes an existing include/exclude rule. The effects are immediate. --refresh refreshes the files on disk based on the sparse rules. This is only necessary if .hg/sparse was changed by hand. --enable-profile and --disable-profile accept a path to a .hgsparse file. This allows defining sparse checkouts and tracking them inside the repository. This is useful for defining commonly used sparse checkouts for many people to use. As the profile definition changes over time, the sparse checkout will automatically be updated appropriately, depending on which changeset is checked out. Changes to .hgsparse are not applied until they have been committed. --import-rules accepts a path to a file containing rules in the .hgsparse format, allowing you to add --include, --exclude and --enable-profile rules in bulk. Like the --include, --exclude and --enable-profile switches, the changes are applied immediately. --clear-rules removes all local include and exclude rules, while leaving any enabled profiles in place. Returns 0 if editing the sparse checkout succeeds. rXrYrnsenable_profilesdisable_profiles import_ruless clear_rulesrlrorpr&stoo many flags specifiedTrr' s/Temporarily Included Files (for merge/rebase): Ns@the debugsparse command is only supported on sparse repositories)rErFresetdeleterJdisableprofileforce)rw)addeddropped conflicting)r byteskwargsr9rcheck_at_most_one_argboolsumrAbortr _has_sparsevfsexistsstatusreadr readtemporaryincludes statusnoi18njoinrLimportfromfiles clearruleswlockmaplistlen refreshwdirr: printchanges)rr5r8rErFrwrJrv importrulesrrurefreshrtactionrLcounttemporaryincludesfcountss r debugsparsersR    %Dhhz"Ghhz"G HHX EHH./MXX01N((?+K.)J XXi Fhhz"G HHX E  * * o~zFP7PfPPP.L tF|, -E qykk!7899D z 88??9 % % IIdhhmmI.6 7 & < rs@D#   "#    H % $F4)2F9.     5 6 jM      5 6 jM      / 0 jM      ? @      . / jM      / 0 jM      * + jM   neQ'L%MN    = >  hq!=>?q9tu:vm}?@vA?@vr