6h RSrSSKJr SSKJr SSKJrJrJrJ r J r J r J r J r 0r\ R"\5rSr\"SSSS \"S 54S S S \"S 54SSS \"S54/\"S5\R"SS9SSj5r\"S/S\R&S9S5rSrSrSrSrSrSrg )aU share a common history between several working directories The share extension introduces a new command :hg:`share` to create a new working directory. This is similar to :hg:`clone`, but doesn't involve copying or linking the storage of the repository. This allows working on different branches or changes in parallel without the associated cost in terms of disk space. Note: destructive operations or extensions like :hg:`rollback` should be used with care as they can result in confusing problems. Automatic Pooled Storage for Clones ----------------------------------- When this extension is active, :hg:`clone` can be configured to automatically share/pool storage across multiple clones. This mode effectively converts :hg:`clone` to :hg:`clone` + :hg:`share`. The benefit of using this mode is the automatic management of store paths and intelligent pooling of related repositories. The following ``share.`` config options influence this feature: ``share.pool`` Filesystem path where shared repository data will be stored. When defined, :hg:`clone` will automatically use shared repository storage instead of creating a store inside each clone. ``share.poolnaming`` How directory names in ``share.pool`` are constructed. "identity" means the name is derived from the first changeset in the repository. In this mode, different remotes share storage if their root/initial changeset is identical. In this mode, the local shared repository is an aggregate of all encountered remote repositories. "remote" means the name is derived from the source repository's path or URL. In this mode, storage is only shared if the path or URL requested in the :hg:`clone` command matches exactly to a repository that was cloned before. The default naming mode is "identity". .. container:: verbose Sharing requirements and configs of source repository with shares: By default creating a shared repository only enables sharing a common history and does not share requirements and configs between them. This may lead to problems in some cases, for example when you upgrade the storage format from one repository but does not set related configs in the shares. Setting `format.exp-share-safe = True` enables sharing configs and requirements. This only applies to shares which are done after enabling the config option. For enabling this in existing shares, enable the config option and reshare. For resharing existing shares, make sure your working directory is clean and there are no untracked files, delete that share and create a new share. ) annotations)_) bookmarkscommandserror extensionshg registrartxnutilutilsships-with-hg-coreshareUsnoupdateNs!do not create a working directoryB bookmarkssalso share bookmarkssrelatives%point to source using a relative paths[-U] [-B] SOURCE [DEST]T) helpcategorynorepoc @[R"UUUU(+UUS9 g)acreate a new shared repository Initialize a new repository and working directory that shares its history (and optionally bookmarks) with another repository. .. note:: using rollback or extensions that destroy/modify history (mq, rebase, etc.) can cause considerable confusion with shared clones. In particular, if two shared clones are both updated to the same changeset, and one of them destroys that changeset with rollback, the other clone will suddenly stop working: all operations will fail with "abort: working directory has unknown parent". The only known workaround is to use debugsetparents on the broken clone to reset it to a changeset that still exists. )destupdaterrelativer)r share)uisourcernoupdaterrs -/usr/lib/python3/dist-packages/hgext/share.pyrr[s*HHH  |  rsunshare)rcUR5(d[R"[S55e[R "X5 g)zmconvert a shared repository to a normal one Copy the store data to the repo and remove the sharedpath data. sthis is not a shared repoN)sharedrAbortrr unshare)rrepos rr r s0 ;;==kk!89::JJrrcURSS5nU(a[R"U5nUURSS5S.US'U"X/UQ70UD6$)Nr pools poolnaming)r#smode shareopts)configr expandpath)origrrargsoptspools rcloner+sY 99Xw 'D t$8]3D  *T *T **rc@[R"[S[5 [R"[RS[ 5 [R"[RS[ 5 [R"[RS[5 g)N _getbkfile _recordchange _writereposclone) r wrapfunctionr getbkfilebmstore recordchange writerepo wrapcommandrtabler+)rs rextsetupr7sZI|Y?I-- MI--|YG8>>8U;rc[R"U5(agURRS5R 5n[ RU;$![ a gf=f)z.Returns whether this repo has shared bookmarksFsshared)rbookmarksinstorevfsread splitlinesFileNotFoundErrorr sharedbookmarks)r!rs r_hassharedbookmarksr?s_!!$''y)446    '' s)A A'&A'c[U5(ac[R"U5nUbJ[R"UR UR S5up4U(aU$UR5 UnU"U5$![a Nf=f)Nr) r?r sharedreposourcer trypendingrootr:closer=)r'r!srcrepofppendings rr1r1s4  %%d+   %00IItxx I D :%  s6A<"A<< B B c^^U"TU5 [TR5(a>[R"TR5mTbSnUR UUU4Sj5 ggg)Nsshare-bookmarksc&>TRT5$N)r/)trselfrEs rrecordchange..s1Ir)r?_repor rA addpostclose)r'rLrKcategoryrEs ` @rr3r3sSrN4::&&%%djj1  )H OOH&I J 'rcU"X5 [UR5(a-[R"UR5nUb U"X5 gggrJ)r?rOr rA)r'rLr!rEs rr4r4sE4::&&%%djj1     'r)NFFF)__doc__ __future__rmercurial.i18nr mercurialrrrrr r r r cmdtablecommand testedwithCATEGORY_REPO_CREATIONrCATEGORY_MAINTENANCEr r+r7r?r1r3r4rrr]s <|#       H % #   {D!$H"IJ |T1%<#=>    6 7    !// "FK !  > R7+G+GH I  +< (:K r