This is an automated email from the ASF dual-hosted git repository.
eamonford pushed a change to branch async-history
in repository https://gitbox.apache.org/repos/asf/incubator-sdap-ingester.git.
discard 495e33b throw a real error
discard 058e432 upgrade pysolr
discard e5d14ec revert
discard 5139bc2 fix tests
discard c46d79a revert
discard 3968bd7 wip
discard a5494ac use shared class
discard 93618e9 async solr history
discard 774f928 log all fs events
add 1e492cf SDAP-279: Collection Manager should poll filesystem for file
updates (#17)
add 7d3dbb4 log all fs events
add 72e6803 async solr history
add 6b17c22 use shared class
add b0663aa wip
add 7fe9aa0 revert
add 8c35cf8 fix tests
add e4c2234 revert
add a51e741 upgrade pysolr
add 77d11e0 throw a real error
add af0f616 cleanup
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 (495e33b)
\
N -- N -- N refs/heads/async-history (af0f616)
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:
.../collection_manager/services/CollectionWatcher.py | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
