Show More
@@ -72,7 +72,7 b' def computemutable(repo):' | |||
|
72 | 72 | def computeimpactable(repo): |
|
73 | 73 | """Everything impactable by mutable revision |
|
74 | 74 | |
|
75 | The mutable filter still have some chance to get invalidated. This will | |
|
75 | The immutable filter still have some chance to get invalidated. This will | |
|
76 | 76 | happen when: |
|
77 | 77 | |
|
78 | 78 | - you garbage collect hidden changeset, |
@@ -751,14 +751,14 b' Commit with multi-line message and custo' | |||
|
751 | 751 | |
|
752 | 752 | |Note: |
|
753 | 753 | | |
|
754 |
| After the last rollback, the " |
|
|
754 | | After the last rollback, the "served" branchheads cache became invalid, but | |
|
755 | 755 | | all changesets in the repo were public. For filtering this means: |
|
756 |
| "mutable" == " |
|
|
756 | | "immutable" == "served" == ø. | |
|
757 | 757 | | |
|
758 |
| As the " |
|
|
759 |
| no update is needed between "mutable" and " |
|
|
758 | | As the "served" cache is invalid, we fall back to the "immutable" cache. But | |
|
759 | | no update is needed between "immutable" and "served" and the "served" cache | |
|
760 | 760 | | is not updated on disk. The on-disk version therefore stays invalid for some |
|
761 |
| time. This explains why the " |
|
|
761 | | time. This explains why the "served" branchheads cache is detected as | |
|
762 | 762 | | invalid here. |
|
763 | 763 | |
|
764 | 764 | $ hg --debug commit -l log -d '2 0' -u 'User Name <user@example.com>' |
@@ -173,7 +173,7 b' visible shared between the initial repo ' | |||
|
173 | 173 | |
|
174 | 174 | :note: The "(+1 heads)" is wrong as we do not had any visible head |
|
175 | 175 | |
|
176 |
check that branch cache with " |
|
|
176 | check that branch cache with "served" filter are properly computed and stored | |
|
177 | 177 | |
|
178 | 178 | $ ls ../push-dest/.hg/cache/branchheads* |
|
179 | 179 | ../push-dest/.hg/cache/branchheads-served |
General Comments 0
You need to be logged in to leave comments.
Login now