This is an automated email from the ASF dual-hosted git repository.
eamonford pushed a change to branch s3-support
in repository https://gitbox.apache.org/repos/asf/incubator-sdap-ingester.git.
discard 7251626 wip
discard a20e85d Collection.py should support s3 path schemes
discard 53180f2 wip
discard 000d93d Create S3Observer
discard 6bca5b8 Move directory scanning out of Collection class
discard 38b254c Make some public methods private, for clarity
add 2c4c8bb SDAP-291: Fix netcdf parsing error by freezing pandas at
1.0.4 (#20)
new f71f6df Make some public methods private, for clarity
new 3c39c30 Move directory scanning out of Collection class
new e26891a Create S3Observer
new 7adb71c wip
new 0f51ebb Collection.py should support s3 path schemes
new c56cd91 wip
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 (7251626)
\
N -- N -- N refs/heads/s3-support (c56cd91)
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 6 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:
granule_ingester/conda-requirements.txt | 1 +
1 file changed, 1 insertion(+)
