This is an automated email from the ASF dual-hosted git repository.
grossws pushed a change to branch logging-refactoring
in repository https://gitbox.apache.org/repos/asf/tika.git
discard 34687cdb0 Migrate tika-parsers-standard-modules to tika-logging
discard 12ca313d0 Migrate tika-app to tika-logging
discard 6b95dd2f3 Implement tika-logging-*
discard 9fcc90a00 fixup! Replace commons-logging with jcl-over-slf4j
discard cefe93a29 Replace commons-logging with jcl-over-slf4j
add ce625326c Replace commons-logging with jcl-over-slf4j
new 3deed200f Implement tika-logging-*
new 3b112e6e7 Migrate tika-app to tika-logging
new 8270a5c51 Migrate tika-parsers-standard-modules to tika-logging
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 (34687cdb0)
\
N -- N -- N refs/heads/logging-refactoring (8270a5c51)
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.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
