This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/project/ch.qos.logback-logback-core-1.2.9
in repository https://gitbox.apache.org/repos/asf/jclouds.git
discard a076b63196 Bump logback-core from 1.1.2 to 1.2.9 in /project
add bcf3b64a2c Update README copyright dates and AzureBlob README
add 2d893aec33 Bump logback-classic from 1.1.2 to 1.2.0 in /project
add c0b1603656 Bump logback-core from 1.1.2 to 1.2.9 in /project
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 (a076b63196)
\
N -- N -- N
refs/heads/dependabot/maven/project/ch.qos.logback-logback-core-1.2.9
(c0b1603656)
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:
README.md | 2 +-
providers/azureblob/README.md | 13 +++++++++++++
providers/azureblob/README.txt | 6 ------
3 files changed, 14 insertions(+), 7 deletions(-)
create mode 100644 providers/azureblob/README.md
delete mode 100644 providers/azureblob/README.txt
