This is an automated email from the ASF dual-hosted git repository.
tallison pushed a change to branch TIKA-4556
in repository https://gitbox.apache.org/repos/asf/tika.git
discard a149a3f62 TIKA-4327: update cxf
discard 6adb03214 TIKA-4327: update aws
discard 96e4c52fc TIKA-4327: update release plugin
discard 182e6dda3 TIKA-4327: use azure bom
discard 31018ad65 TIKA-4556 -- refactor client/server protocol in tika-pipes
add 6867795f2 TIKA-4327: use azure bom
add abb823285 TIKA-4327: update release plugin
add 5b700a573 TIKA-4327: update aws
add 1fa60c5ea TIKA-4327: update cxf
add 002ecb480 TIKA-4556 -- refactor client/server protocol in tika-pipes
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 (a149a3f62)
\
N -- N -- N refs/heads/TIKA-4556 (002ecb480)
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:
