This is an automated email from the ASF dual-hosted git repository.
tallison pushed a change to branch TIKA-4656-allow-content-only
in repository https://gitbox.apache.org/repos/asf/tika.git
omit c5e345e559 TIKA-4656 checkstyle
omit 1da8ca3513 Merge remote-tracking branch
'origin/TIKA-4653-markdown-handler' into TIKA-4656-allow-content-only
omit 49c790630a TIKA-4656 checkstyle
omit f9842f91b0 TIKA-4656 and clean up md integration
omit 1bc86c4699 TIKA-4656 and clean up md integration
omit a637abb926 TIKA-4653 - add markdown contenthandler
omit 96a6d3c2b0 TIKA-4653 - add markdown contenthandler
add 9f97a5e594 TIKA-4656 - add content-only parse mode, markdown handler
integration, and docs
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 (c5e345e559)
\
N -- N -- N refs/heads/TIKA-4656-allow-content-only (9f97a5e594)
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:
