# HG changeset patch
# User Pierre-Yves David <pierre-yves.david@logilab.fr>
# Date 1358793615 -3600
# Node ID 9fb4b2c19bd8de35e6a1f895604b1fd60e6c9e44
# Parent  469ccfe7aa92d258897ffda7411ac574df007435
documentation: update to new filter names

Changeset f3b21beb9802 change filter names but forgot some documentation
updates.

[ original upstream description ]

diff -r 469ccfe7aa92 -r 9fb4b2c19bd8 tests/test-keyword.t
--- a/tests/test-keyword.t	Fri Jan 18 01:23:51 2013 +0100
+++ b/tests/test-keyword.t	Mon Jan 21 19:40:15 2013 +0100
@@ -751,14 +751,14 @@
 
 |Note:
 |
-| After the last rollback, the "unserved" branchheads cache became invalid, but
+| After the last rollback, the "served" branchheads cache became invalid, but
 | all changesets in the repo were public. For filtering this means:
-|   "mutable" == "unserved" == ø.
+|   "immutable" == "served" == ø.
 |
-| As the "unserved" cache is invalid, we fall back to the "mutable" cache. But
-| no update is needed between "mutable" and "unserved" and the "unserved" cache
+| As the "served" cache is invalid, we fall back to the "immutable" cache. But
+| no update is needed between "immutable" and "served" and the "served" cache
 | is not updated on disk. The on-disk version therefore stays invalid for some
-| time. This explains why the "unserved" branchheads cache is detected as
+| time. This explains why the "served" branchheads cache is detected as
 | invalid here.
 
   $ hg --debug commit -l log -d '2 0' -u 'User Name <user@example.com>'