This is an automated email from the ASF dual-hosted git repository.
eamonford pushed a change to branch dockerize_collection_ingester
in repository https://gitbox.apache.org/repos/asf/incubator-sdap-ingester.git.
discard 9840ca3 args
discard 6a89f77 dockerfile
discard 88e0b40 SDAP-254, SDAP-255, SDAP-256: Fix bug where ingestion history
is not saved, fix bug where messages published to RabbitMQ are incorrect, fix
bug where bad collection config file crashes app
add e0a23c4 SDAP-254, SDAP-255, SDAP-256: Fix bug where ingestion history
is not saved, fix bug where messages published to RabbitMQ are incorrect, fix
bug where bad collection config file crashes app
new 213ee5c dockerfile
new 32524d7 args
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 (9840ca3)
\
N -- N -- N refs/heads/dockerize_collection_ingester (32524d7)
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 2 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:
collection_manager/collection_manager/services/CollectionWatcher.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)