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 11f56c6 generate docs for 5e177ffe
omit 5e177ff CASSANDRA-17317: January 2022 blog "Tightening Security for
Apache Cassandra Part: 1"
add 395d33b January 2022 blog "Tightening Security for Apache Cassandra
Part: 1"
new 3bee802 generate docs for 395d33b7
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 (11f56c6)
\
N -- N -- N refs/heads/asf-staging (3bee802)
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/search-index.js | 2 +-
site-ui/build/ui-bundle.zip | Bin 4740084 -> 4740084 bytes
2 files changed, 1 insertion(+), 1 deletion(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
