| 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 : /usr/lib64/python3.9/site-packages/mercurial/__pycache__/ |
Upload File : |
a
�+�bM� � @ s� d dl mZmZ d dlZd dlZddlmZ ddlmZm Z ddl
m Z m
Z G dd� de�Zd d
� Zd d � ZdAd
d�Zdd� Zdd� Zdd� Zdd� Zdd� ZdBdd�Zdd � Zd d � Zd d � Z d!d"� Z d#d$� Z d%d&� Z d'd(� Z e!d)d*�Z"e!d+d*�Z#e!d,d*�Z$e!d-d*�Z%e!d.d*�Z&e!d/d*�Z'e!d0d*�Z(e!d1d*�Z)e!d0d*�Z*e�+d2�Z,e�+d3�Z-d4d5� Z.d6d7� Z/d8d9� Z0d:d;� Z1d<d=� Z2d>Z3d?d@� Z4dS )C� )�absolute_import�print_functionN� )�nullrev)�error�util)�flagutil�sidedatac @ s e Zd ZdZd3dd�Zdd� Zedd� �Zej d d
� �Z
d d � Z d
d� Z ej dd� �Z
dd� Zdd� Zej dd� �Zdd� Zdd� Zej dd � �Zd d � Zd d � Zej d!d"� �Zd#d$� Zd%d&� Zej d'd(� �Zd)d*� Zd+d,� Zej d-d.� �Z d/d0� Z d1d2� Z dS )4�
ChangingFilesaz A class recording the changes made to files by a changeset
Actions performed on files are gathered into 3 sets:
- added: files actively added in the changeset.
- merged: files whose history got merged
- removed: files removed in the revision
- salvaged: files that might have been deleted by a merge but were not
- touched: files affected by the merge
and copies information is held by 2 mappings
- copied_from_p1: {"<new-name>": "<source-name-in-p1>"} mapping for copies
- copied_from_p2: {"<new-name>": "<source-name-in-p2>"} mapping for copies
See their inline help for details.
Nc C s� t |d u rdn|�| _t |d u r$dn|�| _t |d u r:dn|�| _t |d u rPdn|�| _t |d u rfdn|�| _| j�| j� | j�| j� | j�| j� t|d u r�dn|�| _t|d u r�dn|�| _ d S )N� )
�set�_added�_merged�_removed�_touched� _salvaged�update�dict�
_p1_copies�
_p2_copies)�self�touched�added�removed�merged�salvagedZ p1_copiesZ p2_copiesr r �8/usr/lib64/python3.9/site-packages/mercurial/metadata.py�__init__- s
zChangingFiles.__init__c C sT | j |j koR| j|jkoR| j|jkoR| j|jkoR| j|jkoR| j|jkoR| j|jkS �N)r r r r r �copied_from_p1�copied_from_p2)r �otherr r r �__eq__B s
�
�
�
�
�
�zChangingFiles.__eq__c C s" t | jp | jp | jp | jp | j�S r )�boolr r r r r �r r r r �has_copies_infoM s ����z ChangingFiles.has_copies_infoc C s
t | j�S )aK files actively added in the changeset
Any file present in that revision that was absent in all the changeset's
parents.
In case of merge, this means a file absent in one of the parents but
existing in the other will *not* be contained in this set. (They were
added by an ancestor)
)� frozensetr
r$ r r r r W s zChangingFiles.addedc C s* dt | �v r| `| j�|� | �|� d S )Nr )�varsr r
�add� mark_touched�r �filenamer r r �
mark_addedd s zChangingFiles.mark_addedc C s |D ]}| � |� qd S r )r, �r � filenames�fr r r � update_addedj s zChangingFiles.update_addedc C s
t | j�S )z�files actively merged during a merge
Any modified files which had modification on both size that needed merging.
In this case a new filenode was created and it has two parents.
)r& r r$ r r r r n s zChangingFiles.mergedc C s* dt | �v r| `| j�|� | �|� d S )Nr )r' r r r( r) r* r r r � mark_mergedx s zChangingFiles.mark_mergedc C s |D ]}| � |� qd S r )r1 r- r r r �
update_merged~ s zChangingFiles.update_mergedc C s
t | j�S )a files actively removed by the changeset
In case of merge this will only contain the set of files removing "new"
content. For any file absent in the current changeset:
a) If the file exists in both parents, it is clearly "actively" removed
by this changeset.
b) If a file exists in only one parent and in none of the common
ancestors, then the file was newly added in one of the merged branches
and then got "actively" removed.
c) If a file exists in only one parent and at least one of the common
ancestors using the same filenode, then the file was unchanged on one
side and deleted on the other side. The merge "passively" propagated
that deletion, but didn't "actively" remove the file. In this case the
file is *not* included in the `removed` set.
d) If a file exists in only one parent and at least one of the common
ancestors using a different filenode, then the file was changed on one
side and removed on the other side. The merge process "actively"
decided to drop the new change and delete the file. Unlike in the
previous case, (c), the file included in the `removed` set.
Summary table for merge:
case | exists in parents | exists in gca || removed
(a) | both | * || yes
(b) | one | none || yes
(c) | one | same filenode || no
(d) | one | new filenode || yes
)r& r r$ r r r r � s "zChangingFiles.removedc C s* dt | �v r| `| j�|� | �|� d S )Nr )r' r r r( r) r* r r r � mark_removed� s zChangingFiles.mark_removedc C s |D ]}| � |� qd S r )r3 r- r r r �update_removed� s z ChangingFiles.update_removedc C s
t | j�S )a. files that might have been deleted by a merge, but still exists.
During a merge, the manifest merging might select some files for
removal, or for a removed/changed conflict. If at commit time the file
still exists, its removal was "reverted" and the file is "salvaged"
)r& r r$ r r r r � s zChangingFiles.salvagedc C s* dt | �v r| `| j�|� | �|� d S )Nr )r' r r r( r) r* r r r �
mark_salvaged� s zChangingFiles.mark_salvagedc C s |D ]}| � |� qd S r )r5 r- r r r �update_salvaged� s z ChangingFiles.update_salvagedc C s
t | j�S )z0files either actively modified, added or removed)r& r r$ r r r r � s zChangingFiles.touchedc C s dt | �v r| `| j�|� d S )Nr )r' r r r( r* r r r r) � s zChangingFiles.mark_touchedc C s |D ]}| � |� qd S r )r) r- r r r �update_touched� s z ChangingFiles.update_touchedc C s
| j �� S r )r �copyr$ r r r r � s z ChangingFiles.copied_from_p1c C s dt | �v r| `|| j|< d S )Nr )r' r r �r �source�destr r r �mark_copied_from_p1� s z!ChangingFiles.mark_copied_from_p1c C s" |� � D ]\}}| �||� qd S r )�itemsr< �r �copiesr; r: r r r �update_copies_from_p1� s z#ChangingFiles.update_copies_from_p1c C s
| j �� S r )r r8 r$ r r r r � s z ChangingFiles.copied_from_p2c C s dt | �v r| `|| j|< d S )Nr )r' r r r9 r r r �mark_copied_from_p2� s z!ChangingFiles.mark_copied_from_p2c C s" |� � D ]\}}| �||� qd S r )r= rA r> r r r �update_copies_from_p2� s z#ChangingFiles.update_copies_from_p2)NNNNNNN) �__name__�
__module__� __qualname__�__doc__r r" �propertyr% r Z
propertycacher r, r0 r r1 r2 r r3 r4 r r5 r6 r r) r7 r r< r@ r rA rB r r r r r
sP �
#
r
c C s� | � � }| �� }|�� tkr0|�� tkr0t| �S |�� tkrR|�� tkrRt|| �S |�� tkrx|�� tkrxt|| dd�S |�� |�� kr�t|| �S t||| �S dS )z'compute the files changed by a revision� )�parentN)�p1�p2�revr �
_process_root�_process_linear�_process_merge��ctxrJ rK r r r �compute_all_files_changes� s
rR c C s& t � }| �� }|D ]}|�|� q|S )zEcompute the appropriate changed files for a changeset with no parents)r
�manifestr, )rQ �mdrS r+ r r r rM � s
rM c
C s� t � }| �� }|�� }g }|�|��� D ]T\}}|d d du rL|�|� q(|�|� |d d du rr|�|� q(|�|� q(|dkr�|j} n |dkr�|j } nds�J d| ��|D ]&}|| �
� }
|
r�|
\} } | | |� q�|S )zJcompute the appropriate changed files for a changeset with a single parentr r NrH Fzbad parent value %d) r
rS �diffr= r3 �appendr, r) r< rA �renamed)
Z
parent_ctxZ children_ctxrI rT Zparent_manifestZchildren_manifestZcopies_candidater+ �d�copied� copy_infor: �srcnoder r r rN s,
rN c s~ � � � }t� }� �� }| �� }|�� }|�|�}|�|�} � � � j�| �� |�� �}
|
s^tg}
� fdd�|
D �} g } |�� D �]`\�}
| � �d�}|du r�t
|| �|
� q||
d d du r�|d d du r�|� �� | � �� q||
d d du �r|d d du �r|�
�� q||
d d du�r�|d d du�r�|
d d du �sX|d d du �r�t�fdd�| D ���r||��� n
|��� n>|j�|
d d d�}|�� �� tk�r�|��� n
|��� | � �� q|d s|J d
��q|| �� D ]\�}t
|| �|� �q�| D ]r�� � �� }|�r|\}}|| v �rN| | �� |k�rN|�|�� n(||v �r|| �� |k�r|�|�� �q|S ) u� compute the appropriate changed files for a changeset with two parents
This is a more advance case. The information we need to record is summarise
in the following table:
┌──────────────┬──────────────┬──────────────┬──────────────┬──────────────┐
│ diff ╲ diff │ ø │ (Some, None) │ (None, Some) │ (Some, Some) │
│ p2 ╲ p1 │ │ │ │ │
├──────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ │ │🄱 No Changes │🄳 No Changes │ │
│ ø │🄰 No Changes │ OR │ OR │🄵 No Changes │
│ │ │🄲 Deleted[1] │🄴 Salvaged[2]│ [3] │
├──────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ │🄶 No Changes │ │ │ │
│ (Some, None) │ OR │🄻 Deleted │ ø │ ø │
│ │🄷 Deleted[1] │ │ │ │
├──────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ │🄸 No Changes │ │ │ 🄽 Touched │
│ (None, Some) │ OR │ ø │🄼 Added │OR 🅀 Salvaged │
│ │🄹 Salvaged[2]│ │ (copied?) │ (copied?) │
├──────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ │ │ │ 🄾 Touched │ 🄿 Merged │
│ (Some, Some) │🄺 No Changes │ ø │OR 🅁 Salvaged │OR 🅂 Touched │
│ │ [3] │ │ (copied?) │ (copied?) │
└──────────────┴──────────────┴──────────────┴──────────────┴──────────────┘
Special case [1]:
The situation is:
- parent-A: file exists,
- parent-B: no file,
- working-copy: no file.
Detecting a "deletion" will depend on the presence of actual change on
the "parent-A" branch:
Subcase 🄱 or 🄶 : if the state of the file in "parent-A" is unchanged
compared to the merge ancestors, then parent-A branch left the file
untouched while parent-B deleted it. We simply apply the change from
"parent-B" branch the file was automatically dropped.
The result is:
- file is not recorded as touched by the merge.
Subcase 🄲 or 🄷 : otherwise, the change from parent-A branch were explicitly dropped and
the file was "deleted again". From a user perspective, the message
about "locally changed" while "remotely deleted" (or the other way
around) was issued and the user chose to deleted the file.
The result:
- file is recorded as touched by the merge.
Special case [2]:
The situation is:
- parent-A: no file,
- parent-B: file,
- working-copy: file (same content as parent-B).
There are three subcases depending on the ancestors contents:
- A) the file is missing in all ancestors,
- B) at least one ancestor has the file with filenode ≠ from parent-B,
- C) all ancestors use the same filenode as parent-B,
Subcase (A) is the simpler, nothing happend on parent-A side while
parent-B added it.
The result:
- the file is not marked as touched by the merge.
Subcase (B) is the counter part of "Special case [1]", the file was
modified on parent-B side, while parent-A side deleted it. However this
time, the conflict was solved by keeping the file (and its
modification). We consider the file as "salvaged".
The result:
- the file is marked as "salvaged" by the merge.
Subcase (C) is subtle variation of the case above. In this case, the
file in unchanged on the parent-B side and actively removed on the
parent-A side. So the merge machinery correctly decide it should be
removed. However, the file was explicitly restored to its parent-B
content before the merge was commited. The file is be marked
as salvaged too. From the merge result perspective, this is similar to
Subcase (B), however from the merge resolution perspective they differ
since in (C), there was some conflict not obvious solution to the
merge (That got reversed)
Special case [3]:
The situation is:
- parent-A: file,
- parent-B: file (different filenode as parent-A),
- working-copy: file (same filenode as parent-B).
This case is in theory much simple, for this to happens, this mean the
filenode in parent-A is purely replacing the one in parent-B (either a
descendant, or a full new file history, see changeset). So the merge
introduce no changes, and the file is not affected by the merge...
However, in the wild it is possible to find commit with the above is not
True. For example repository have some commit where the *new* node is an
ancestor of the node in parent-A, or where parent-A and parent-B are two
branches of the same file history, yet not merge-filenode were created
(while the "merge" should have led to a "modification").
Detecting such cases (and not recording the file as modified) would be a
nice bonus. However do not any of this yet.
c s g | ]}� � � | �� �qS r ��reporS ��.0�r�rQ r r �
<listcomp>� � z"_process_merge.<locals>.<listcomp>Nr r c 3 s | ]}t |� �d uV qd S r ��_find�r_ Zma�r+ r r � <genexpr>� rc z!_process_merge.<locals>.<genexpr>)ZfileidF� unreachable)r] r
rS rU � changelog�commonancestorsheads�noder r= �pop�_process_other_unchangedr, rV r3 �anyr5 r) ZfilectxrK rL r1 rW �filenoder< rA )Zp1_ctxZp2_ctxrQ r] rT �mZp1mZp2mZdiff_p1Zdiff_p2�cahs�masZcopy_candidatesZd1Zd2�fctxrZ r: r[ r )rQ r+ r rO . sZ o
�
$ $$
rO c C s || vr dS | � |�d S )z%return the associate filenode or NoneNr ��find)rS r+ r r r re � s re c s� |d d �|d d }�d urL|d u rLt � �fdd�|D ��r�| �� � nP�d u r~|d ur~t � fdd�|D ��r�| �� � n �d ur�|d ur�n ds�J d��d S )Nr r c 3 s | ]}t |� ��k V qd S r rd rf �r+ Z source_noder r rh � rc z+_process_other_unchanged.<locals>.<genexpr>c 3 s | ]}t |� �d uV qd S r rd rf rg r r rh � rc Fri )ro r3 r5 )rT rs r+ rU Z target_noder rw r rn � s rn c s t � fdd�| D ��S )Nc 3 s | ]}t |� �d u V qd S r rd rf rg r r rh rc z._missing_from_all_ancestors.<locals>.<genexpr>��all)rs r+ r rg r �_missing_from_all_ancestors s rz c s: g }| � � D ](� t� fdd�| �� D ��s |�� � q |S )z-return the list of files added in a changesetc 3 s | ]}� |v V qd S r r )r_ �p�r/ r r rh rc z-computechangesetfilesadded.<locals>.<genexpr>)�filesro �parentsrV )rQ r r r| r �computechangesetfilesadded s
r c s` |dur|\����n � � � �� �� ���� ���� �tj� ��fdd������fdd�}|S )a< return a function to detect files "wrongly" detected as `removed`
When a file is removed relative to p1 in a merge, this
function determines whether the absence is due to a
deletion from a parent, or whether the merge commit
itself deletes the file. We decide this by doing a
simplified three way merge of the manifest entry for
the file. There are two ways we decide the merge
itself didn't delete a file:
- neither parent (nor the merge) contain the file
- exactly one parent contains the file, and that
parent has the same filelog entry as the merge
ancestor (or all of them if there two). In other
words, that parent left the file unchanged while the
other one deleted it.
One way to think about this is that deleting a file is
similar to emptying it, so the list of changed files
should be similar either way. The computation
described above is not done directly in _filecommit
when creating the list of changed files, however
it does something very similar by comparing filelog
nodes.
Nc s> �� � } �� � }� �� j�| |�}|s,tg}� fdd�|D �S )Nc s g | ]}� � � | �� �qS r r\ r^ ra r r rb C rc z3get_removal_filter.<locals>.mas.<locals>.<listcomp>)rl r] rj rk r )Zp1nZp2nrr rP r r rs < s z get_removal_filter.<locals>.masc sT � �v r*� �vo(t � �fdd��� D ��S � �v rLt � �fdd��� D ��S dS d S )Nc 3 s* | ]"}� |v o |� � ��� � �kV qd S r ru rf )r/ �m1r r rh G s zAget_removal_filter.<locals>.deletionfromparent.<locals>.<genexpr>c 3 s* | ]"}� |v o |� � ��� � �kV qd S r ru rf )r/ �m2r r rh K rc Trx r| )r� r� rs r| r �deletionfromparentE s �z.get_removal_filter.<locals>.deletionfromparent)rJ rK rS r Z cachefunc)rQ �xr� r )rQ r� r� rs rJ rK r �get_removal_filter s
r� c sF g }| � � D ]}|| vr |�|� q |rBt| �� � fdd�|D �}|S )z/return the list of files removed in a changesetc s g | ]}� |�s|�qS r r r^ �Zrfr r rb Z rc z0computechangesetfilesremoved.<locals>.<listcomp>)r} rV r� )rQ r r/ r r� r � computechangesetfilesremovedR s r� c C sd g }t | �� �dk r|S | �� D ]>}|| v r | | }|j�|j�}|d | �� jkr |�|� q |S )z.return the list of files merged in a changesetrH r )�lenr~ r} Z_filelogZ _filenoder] ZnullidrV )rQ r r/ rt r~ r r r �computechangesetfilesmerged^ s r� c
C s� i }i }| � � }| �� }| j�� }| �� D ]r}||�r*|| vr@q*| | �� }|sRq*|\}} ||v r||| �� | kr||||< q*||v r*|| �� | kr*|||< q*||fS )z�return the copies data for a changeset
The copies data are returned as a pair of dictionnary (p1copies, p2copies).
Each dictionnary are in the form: `{newname: oldname}`
)rJ rK Z_repo� narrowmatchr} rW rp )
rQ Zp1copiesZp2copiesrJ rK r� �dstrY �srcr[ r r r �computechangesetcopiesl s"
r� c C sX g }t | �D ]&\}}||v r |�d||| f � q t|�t|�krNt�d��d�|�S )Ns %d %ss( some copy targets missing from file list�
)� enumeraterV r� r ZProgrammingError�join)r} r? r= �ir� r r r � encodecopies� s �r� c C sh zJi }|s|W S |� d�D ]*}|� d�\}}t|�}| | }|||< q|W S ttfyb Y d S 0 d S )Nr� � )�split�int�
ValueError�
IndexError)r} �datar? �l�strindexr� r� r� r r r � decodecopies� s
r� c C s> t |�}g }t| �D ] \}}||v r|�d| � qd�|�S )Ns %dr� )r r� rV r� )r} �subset�indicesr� r/ r r r �encodefileindices� s r� c C st zVg }|s|W S |� d�D ]6}t|�}|dk s:|t| �krB W d S |�| | � q|W S ttfyn Y d S 0 d S )Nr� r )r� r� r� rV r� r� )r} r� r� r� r� r r r �decodefileindices� s r� Z11100rH Z00100Z01000Z01100Z10000Z10100Z11Z10z>Lz>bLLc
C s\ t | j�}|�| j�� � |�| j�� � t|�}dd� t|�D �}d|d < t� t
|��g}d}|D ]�}t
|�}||7 }d}|| j v r�|t O }nN|| j
v r�|tO }n:|| jv r�|tO }n&|| jv r�|tO }n|| jv r�|tO }d }|| jv �r|tO }| j�|�}n || jv �r$| j�|�}|tO }|| } |�t� ||| �� qd|�|� tjd� |�iS )Nc S s i | ]\}}||�qS r r )r_ r� r/ r r r �
<dictcomp>� rc z)encode_files_sidedata.<locals>.<dictcomp>r rc ) r r r r �valuesr �sortedr� � INDEX_HEADER�packr� r �
ADDED_FLAGr � MERGED_FLAGr � REMOVED_FLAGr �
SALVAGED_FLAG� TOUCHED_FLAG�COPIED_FROM_P1_FLAG�get�COPIED_FROM_P2_FLAGrV � INDEX_ENTRY�extend� sidedatamod�SD_FILESr� )
r} � all_filesZfile_idx�chunksZfilename_lengthr/ Z
filename_size�flagr8 �copy_idxr r r �encode_files_sidedata� sB
r� c C s� t � }| �tj�}|d u r |S g }g }t|�tjks8J �t�|d�d }tj}|tj| }|}t|�|kspJ �t |�D �] } t�||�\}
} } | |7 } ||| � }
| | }t|
�|ks�J �|tj7 }| }|�
|
� |
t @ t kr�|�
|
� nf|
t @ tk�r|�|
� nL|
t @ tk�r |�|
� n2|
t @ tk�r:|�|
� n|
t @ tk�rR|�|
� d }|
t@ tk�rl|j}n|
t@ tk�r�|j}|d urx|�
||
| f� qx|D ]\}}
} ||| |
� �q�|S �Nr )r
r� r� r� r� r� �size� unpack_fromr� �rangerV � ACTION_MASKr� r, r� r1 r� r3 r� r5 r� r) � COPIED_MASKr� r< r� rA )r rT �rawr? r� Z total_files�offsetZfile_offset_baseZfile_offset_last�idxr� Zfile_endr� r+ ZfilesizerY r r r �decode_files_sidedata� sR
r� c C s | | }t |�}t|�|jfS r )rR r� r% )�srcreporL rQ r} r r r � _getsidedata- s r� c C s( t | |�\}}|rtjnd}||dffS r� )r� � sidedataflag�REVIDX_HASCOPIESINFO)r] �revlogrL Zexisting_sidedatar r% Z flags_to_addr r r �copies_sidedata_computer3 s r� c C sN |� � |�� }|durBt| |�}|�||f� |� � |�� }q|�� dS )a� The function used by worker precomputing sidedata
It read an input queue containing revision numbers
It write in an output queue containing (rev, <sidedata-map>)
The `None` input value is used as a stop signal.
The `tokens` semaphore is user to avoid having too many unprocessed
entries. The workers needs to acquire one token before fetching a task.
They will be released by the consumer of the produced data.
N)�acquirer� r� �put�release)r� Z
revs_queueZsidedata_queue�tokensrL r� r r r �_sidedata_worker9 s
r� �2 c s� ddl m} |�| j�}t�|t ��t�� }t�� � | jdu sDJ �| j �
� D ]}|� |� qNt |�D ]}|� d� qfg }t |�D ]0}| |� �f}tj
t|d�} |�| � | �� q�i �� ��fdd�}
|
S )z�The parallel version of the sidedata computation
This code spawn a pool of worker that precompute a buffer of sidedata
before we actually need themr )�workerN)�target�argsc sh �� |d �}|d u r>� �� \}}||kr>|�|< � �� \}}q ��� |\}}d}|r\tj}||dffS r� )rm r� r� r� r� ) r] r� rL Z old_sidedatar� r` r r% Znew_flag�Z sidedataqZstagingr� r r �sidedata_companion{ s z6_get_worker_sidedata_adder.<locals>.sidedata_companion)� r� Z _numworkersZui�multiprocessing�BoundedSemaphore�BUFF_PER_WORKERZQueueZ
filternamerj Zrevsr� r� ZProcessr� rV �start) r� Zdestrepor� Z nbworkersZrevsqr` r� Z
allworkersr� �wr� r r� r �_get_worker_sidedata_adderS s&
r� )r )N)5Z
__future__r r r� �structrl r r� r r Z revlogutilsr r� r r� �objectr
rR rM rN rO re rn rz r r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� �Structr� r� r� r� r� r� r� r� r� r r r r �<module> sT T
% ?
7
'6