This is an automated email from the ASF dual-hosted git repository.
ppkarwasz pushed a change to branch fix/mongodb-validation
in repository https://gitbox.apache.org/repos/asf/logging-flume-mongodb.git
discard 8e30cc0 Remove unused variable
discard 8ead1fc Validate MongoDB sink configuration
add 9df7d6e Build(deps): bump io.dropwizard.metrics:metrics-core from
4.1.18 to 4.2.39 in the maven-minor-updates group across 1 directory (#9)
add e1aa4e7 Validate MongoDB sink configuration
add 4b6d135 Remove unused variable
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 (8e30cc0)
\
N -- N -- N refs/heads/fix/mongodb-validation (4b6d135)
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:
pom.xml | 2 +-
...ongodb_sink.xml => update_io.dropwizard.metrics_metrics-core.xml} | 5 +++--
2 files changed, 4 insertions(+), 3 deletions(-)
copy src/changelog/.2.x.x/{add_mongodb_sink.xml =>
update_io.dropwizard.metrics_metrics-core.xml} (56%)
