This is an automated email from the ASF dual-hosted git repository.

jsedding pushed a change to branch 
jsedding/OAK-11861-segment-parallel-initialization
in repository https://gitbox.apache.org/repos/asf/jackrabbit-oak.git


 discard 9e62147c8d OAK-11861 - segment store initialization should run in 
parallel
     add 6bd93ba2a8 OAK-11832 : replaced Guava's TreeTraversal with OAK Commons 
- fix Import in testcase
     add 7377c95bbe OAK-11861 - segment store initialization should run in 
parallel

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   (9e62147c8d)
            \
             N -- N -- N   
refs/heads/jsedding/OAK-11861-segment-parallel-initialization (7377c95bbe)

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:
 .../oak/commons/concurrent/ForkJoinUtils.java      | 100 +++++++++++++++++++++
 .../oak/commons/concurrent/package-info.java       |   2 +-
 .../jackrabbit/oak/commons/TraverserTest.java      |   2 +-
 .../jackrabbit/oak/segment/file/tar/TarFiles.java  |   5 +-
 .../jackrabbit/oak/segment/file/tar/TarReader.java |   7 --
 5 files changed, 105 insertions(+), 11 deletions(-)
 create mode 100644 
oak-commons/src/main/java/org/apache/jackrabbit/oak/commons/concurrent/ForkJoinUtils.java

Reply via email to