This is an automated email from the ASF dual-hosted git repository.
dzamo pushed a change to branch staging
in repository https://gitbox.apache.org/repos/asf/drill-site.git.
discard 74b9410 Update README and add a Jekyll plugin to kick off
createdatadocs.py.
discard d77e304 Update .asf.yaml.
add 6c6b82c Reduce .asf.yaml to config for this branch only.
add 73e6001 Set jekyll.outputdir in .asf.yaml to /.
new 04ff2d7 Set Jekyll ~> 3.9 constraint in Gemfile.
new 9228379 Update README and add a Jekyll plugin to kick off
createdatadocs.py.
new e86aeda Reset .asf.yaml.
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 (74b9410)
\
N -- N -- N refs/heads/staging (e86aeda)
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 3 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:
.asf.yaml | 6 +++---
Gemfile | 5 +++--
Gemfile.lock | 35 +++++++++++++++++------------------
_config.yml | 7 +++++++
4 files changed, 30 insertions(+), 23 deletions(-)
