ruạṛ
a �+�b+" � @ s� d dl mZ d dlZddlmZ ddlmZmZ ddlm Z mZm Z m Z m Z m Z mZ e�d�Zdd d �Zdd d�Zdd� Zdd� Zdd� Zdd� Zddd�ZdS ) � )�absolute_importN� )�_)�hex�nullrev)�error�node�obsolete�obsutil�revset�scmutil�utils \b[0-9a-f]{6,64}\b� c sd | j j� t|�}||k r6� fdd�|D �}d�|�}n*|�� }td�}|t�� |��|d f; }|S )z�returns a string summarizing revisions in a decent size If there are few enough revisions, we list them all. Otherwise we display a summary of the form: 1ea73414a91b and 5 others c s g | ]}t �� |���qS � )r �short��.0�r�Ztonoder �;/usr/lib64/python3.9/site-packages/mercurial/rewriteutil.py� <listcomp>+ � z _formatrevs.<locals>.<listcomp>s , s %s and %d othersr )Z changelogr �len�join�firstr r )�repo�revsZmaxrevsZnumrevsZshorts�summaryr r r r � _formatrevs s r � rewriteTc C s� t |v r*td�| }td�}tj||d��tdd� |D ��rV| j�d� dd� |D �}t| d �� �d kr|t� td �| ��| � d |�}|r�t | |�}td �||f }td �}tj||d��t | |�}|r�td�}tjtd�|t|�f |d��|s�dS t �| t j��s�t| |�} | �r�| \} } } td�|| | f }| �� | �� k�rV|td�| 7 }| jj�r�| �� | �� k�r�|td�| | f 7 }|td�| | | f 7 }tj|td�d��ntj|td�d��dS )a& check if revs can be rewritten action is used to control the error message. check_divergence allows skipping the divergence checks in cases like adding a prune marker (A, ()) to obsstore (which can't be diverging). Make sure this function is called after taking the lock. s cannot %s the null revisions no changeset checked out)�hintc s s | ]}t �|d �V qdS )�revN)r Z safehasattrr r r r � <genexpr>B r zprecheck.<locals>.<genexpr>s- rewriteutil.precheck called with ctx not revsc s s | ]}|� � V qd S )N)r! r r r r r" D r Nr s" cannot %s changesets while mergings %ld and public()s cannot %s public changesets: %ss see 'hg help phases' for detailss# see 'hg help evolution.instability's7 cannot %s changeset, as that will orphan %d descendantss8 cannot %s %s, as that creates content-divergence with %ss , from %ss0 changeset %s is a successor of changeset %ss� changeset %s already has a successor in changeset %s rewriting changeset %s would create "content-divergence" set experimental.evolution.allowdivergence=True to skip this checksE see 'hg help evolution.instability' for details on content-divergences@ add --verbose for details or see 'hg help evolution.instability')r r r Z InputError�any�uiZ develwarnr �parentsZ StateErrorr r �disallowednewunstabler � isenabledZallowdivergenceopt�_find_new_divergencer! �verbose) r r �actionZcheck_divergence�msgr Z publicrevsr Z newunstableZnew_divergenceZ local_ctxZ other_ctxZbase_ctxr r r �precheck4 s� � �� ��� ��������r, c C s( t �| t j�}|rt�� S | �d||�S )z�Checks whether editing the revs will create new unstable changesets and are we allowed to create them. To allow new unstable changesets, set the config: `experimental.evolution.allowunstable=True` s (%ld::) - %ld)r r' Zallowunstableoptr Zbasesetr )r r Z allowunstabler r r r& � s r& c C sR | � d|�}|D ]<}t| | | �}|r| | | |d | �� |d f S qd S )Ns %ld and obsolete()r r )r �find_new_divergence_from� unfiltered)r r Zobsrevsr Zdivr r r r( � s (r( c C sp |� � s dS t�| |�� �}|r4|d d |�� fS t�| |�}|rh|d d }|d d }|d |fS dS dS )z�return divergent revision if rewriting an obsolete cset (ctx) will create divergence Returns (<other node>, <common ancestor node>) or None Nr s divergentnodess commonpredecessor)r r �successorssetsr Z divergentsets)r �ctxZssetZdivsetsZnsuccsetZprecr r r r- � s r- c C s> | � dd�}|dkrdS |dkr$dS t�td�||f ��d S )Nr s empty-successors skipTs keepFsf %s doesn't know how to handle config rewrite.empty-successor=%s (only 'skip' and 'keep' are supported))Zconfigr Z ConfigErrorr )r$ ZcommandZempty_successorr r r �skip_empty_successor� s ���r1 c C s( |si }i }t �t|�}| �� }|D ]�}zt�||�}W n tjtjfyV Y q$Y n0 |du rbq$|| }|� � s�|� |�} | du r�q$| g} nt j | |� � |d�} t| �dk�rt| d �dk�r| d d } | dur�t| �} |�|| dt|�� �}n| j�td�| � q$| j�td�| � q$|S )a� Replace all obsolete commit hashes in the message with the current hash. If the obsolete commit was split or is divergent, the hash is not replaced as there's no way to know which successor to choose. For commands that update a series of commits in the current transaction, the new obsolete markers can be considered by setting ``pending`` to a mapping of ``pending[oldnode] = [successor_node1, successor_node2,..]``. N)�cacher r sb The stale commit message reference to %s could not be updated (The referenced commit was dropped) s> The stale commit message reference to %s could not be updated )�re�findall�NODE_REr. r Zresolvehexnodeidprefixr ZWdirUnsupportedZAmbiguousPrefixLookupErrorr �getr r/ r r r �replacer$ Znoter ) r Z commitmsg�pendingr2 ZhashesZunfi�hZfullnoder0 Z successors� successorZnewhashr r r �update_hash_refs� sN ������r; )r )r T)N)Z __future__r r3 Zi18nr r r r � r r r r r r �compiler5 r r, r& r( r- r1 r; r r r r �<module> s $ T
cải xoăn