This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git
omit 617569a0d ninja-fix to
Last-Chance-to-Register-Schedule-Moderators-Announced
omit 70a1cf503 generate docs for da82ce99
add 336329a65 ninja-fix to Last Chance to Register: Schedule & Moderators
Announced blog
new db51218eb generate docs for 336329a6
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 (617569a0d)
\
N -- N -- N refs/heads/asf-staging (db51218eb)
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 1 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:
content/_/blog.html | 2 +-
content/search-index.js | 2 +-
site-content/source/modules/ROOT/pages/blog.adoc | 2 +-
...to-Register-Schedule-Moderators-Announced.adoc} | 2 +-
site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078
bytes
5 files changed, 4 insertions(+), 4 deletions(-)
rename
site-content/source/modules/ROOT/pages/blog/{Last-Chance-to-Register-Schedule-&-Moderators-Announced.adoc
=> Last-Chance-to-Register-Schedule-Moderators-Announced.adoc} (91%)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
