You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-commits@jackrabbit.apache.org by da...@apache.org on 2026/10/07 03:57:59 UTC
(jackrabbit-oak) branch issue/OAK-12438 updated (d703052207 -> e7aaf995c5)
This is an automated email from the ASF dual-hosted git repository.
rishabhdaim pushed a change to branch issue/OAK-12438
in repository https://gitbox.apache.org/repos/asf/jackrabbit-oak.git
omit d703052207 OAK-12438: shorten policy comments and explain cache tests
omit 37a9093e3a OAK-12438: remove obsolete shared cache maintenance toggle
omit bc761fec19 OAK-12438: remove obsolete shared toggle tests
omit 9562233331 OAK-12438: verify cache mode isolation and generation sampling
omit 9c714fb60c OAK-12438: clean up the inherited factory toggle test
omit 496e6c47ac OAK-12438: test the registered Segment maintenance override
omit 7843ec0cbf OAK-12438: test the scoped toggle after caller migration
omit 45c8661576 OAK-12438: scope maintenance overrides to Segment Tar caches
omit 70714b2a02 OAK-12436: clarify maintenance comments and test intent
omit 9f25e2643a OAK-12436: verify repeated cache maintenance mode selection
omit 6942dd133b OAK-12436: complete Lucene cache embedding and edge tests
omit 926009be4a OAK-12436: clarify refresh and saturated executor behavior
omit 2629ebe59c OAK-12436: preserve and test existing maintenance behavior
omit a9126cde81 OAK-12436: keep the base PR limited to cache API support
omit 6f29f82905 OAK-12436: publish the complete stack before final review
omit 33cdac3dee OAK-12436: test explicit mode precedence and null validation
omit fb36da5b23 OAK-12436: preserve legacy behavior during bundle migration
omit d2f709381c OAK-12436: support per-cache caffeine maintenance mode
add 163287a135 OAK-12436: add per-cache Caffeine maintenance modes
add e7aaf995c5 OAK-12438: scope Segment Tar cache maintenance policy
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (d703052207)
\
N -- N -- N refs/heads/issue/OAK-12438 (e7aaf995c5)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes: