ruạṛ
a �+�bR � @ s� d dl mZ ddlmZ ddlmZmZmZmZm Z m Z mZ ddlm Z mZ e e e e f e e e e�e�Ze de diZdd � Zd d� Zdd � Zdd� Zdd� Zdd� ZdS )� )�absolute_import� )�_� )�REVIDX_DEFAULT_FLAGS�REVIDX_ELLIPSIS�REVIDX_EXTSTORED�REVIDX_FLAGS_ORDER�REVIDX_HASCOPIESINFO�REVIDX_ISCENSORED�REVIDX_RAWTEXT_CHANGING_FLAGS)�error�utilNc C s t | |t� dS )a! Register a flag processor on a revision data flag. Invariant: - Flags need to be defined in REVIDX_KNOWN_FLAGS and REVIDX_FLAGS_ORDER, and REVIDX_RAWTEXT_CHANGING_FLAGS if they can alter rawtext. - Only one flag processor can be registered on a specific flag. - flagprocessors must be 3-tuples of functions (read, write, raw) with the following signatures: - (read) f(self, rawtext) -> text, bool - (write) f(self, text) -> rawtext, bool - (raw) f(self, rawtext) -> bool "text" is presented to the user. "rawtext" is stored in revlog data, not directly visible to the user. The boolean returned by these transforms is used to determine whether the returned text can be used for hash integrity checking. For example, if "write" returns False, then "text" is used to generate hash. If "write" returns True, that basically means "rawtext" returned by "write" should be used to generate hash. Usually, "write" and "read" return different booleans. And "raw" returns a same boolean as "write". Note: The 'raw' transform is used for changegroup generation and in some debug commands. In this case the transform only indicates whether the contents can be used for hash integrity checks. N)�insertflagprocessor�flagprocessors)�flag� processor� r �D/usr/lib64/python3.9/site-packages/mercurial/revlogutils/flagutil.py�addflagprocessor- s r c C sf | t @ std�| }t�|��| tvr<td�| }t�|��| |v rZtd�| }t�|��||| <