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.
discard d604a2a generate docs for d27bb8c9 add b70dcb8 ninja-fix: add back in files needed that antora is not (yet) generating new 8b34091 generate docs for b70dcb85 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 (d604a2a) \ N -- N -- N refs/heads/asf-staging (8b34091) 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/.htaccess | 58 ++ content/robots.txt | 7 + content/sitemap.xml | 1434 +++++++++++++++++++++++++++++++++++++++++++ site-ui/build/ui-bundle.zip | Bin 4740057 -> 4740057 bytes 4 files changed, 1499 insertions(+) create mode 100644 content/.htaccess create mode 100644 content/robots.txt create mode 100644 content/sitemap.xml --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org