##// END OF EJS Templates
test-keyword: improve grammar and spelling in branchcache note...
Christian Ebert -
r18295:3cdf04e1 default
parent child Browse files
Show More
@@ -750,13 +750,13 b' Commit with multi-line message and custo'
750 |Note:
750 |Note:
751 |
751 |
752 | After the last rollback, the "unserved" branchheads cache became invalid, but
752 | After the last rollback, the "unserved" branchheads cache became invalid, but
753 | all changeset in the repo were public. So filtering wise:
753 | all changesets in the repo were public. For filtering this means:
754 | "mutable" == "unserved" == ø.
754 | "mutable" == "unserved" == ø.
755 |
755 |
756 | As the "unserved" cache is invalid, we fall back to "mutable" cache. But not
756 | As the "unserved" cache is invalid, we fall back to the "mutable" cache. But
757 | update is needed between "mutable" and "unserved" cache and the "unserved"
757 | no update is needed between "mutable" and "unserved" and the "unserved" cache
758 | cache is not updated on disk. The on disk version therefor stay invalid for
758 | is not updated on disk. The on-disk version therefore stays invalid for some
759 | some time. This explains why the "unserved" branchheads cache is detect
759 | time. This explains why the "unserved" branchheads cache is detected as
760 | invalid here.
760 | invalid here.
761
761
762 $ hg --debug commit -l log -d '2 0' -u 'User Name <user@example.com>'
762 $ hg --debug commit -l log -d '2 0' -u 'User Name <user@example.com>'
General Comments 0
You need to be logged in to leave comments. Login now