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 475edb3 generate docs for 868ce6ba add 90be0f4 Update for new Cassandra releases 2.2.19, 3.0.23, 3.11.9, 4.0-beta3 new ae1de50 generate docs for 90be0f45 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 (475edb3) \ N -- N -- N refs/heads/asf-staging (ae1de50) 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/download/index.html | 8 ++++---- content/feed.xml | 2 +- content/index.html | 2 +- src/_data/releases.yaml | 16 ++++++++-------- 4 files changed, 14 insertions(+), 14 deletions(-) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org