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 1a2d8dcc generate docs for 8fd077a6
     add c630db6b WEBSITE - Liquibase case study + blog, April 2022
     new 99983795 generate docs for c630db6b

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   (1a2d8dcc)
            \
             N -- N -- N   refs/heads/asf-staging (99983795)

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:
 ...ssandra-4.0-users-unsplash-eden-constantino.jpg | Bin 0 -> 2324403 bytes
 content/_/_images/companies/liquibase.svg          |   1 +
 content/_/blog.html                                |  24 +++++
 ...e-is-Ready-to-Support-Cassandra-4.0-Users.html} |  40 ++------
 content/_/case-studies.html                        |  26 +++++
 .../Liquibase.html}                                | 113 ++++++++-------------
 .../4.1/cassandra/tools/nodetool/bootstrap.html    |   8 +-
 .../doc/4.1/cassandra/tools/nodetool/import.html   |   6 +-
 .../doc/4.1/cassandra/tools/nodetool/nodetool.html |   9 +-
 .../4.1/cassandra/tools/nodetool/repair_admin.html |  86 ++++++++--------
 .../latest/cassandra/tools/nodetool/bootstrap.html |   8 +-
 .../latest/cassandra/tools/nodetool/import.html    |   6 +-
 .../latest/cassandra/tools/nodetool/nodetool.html  |   9 +-
 .../cassandra/tools/nodetool/repair_admin.html     |  86 ++++++++--------
 .../trunk/cassandra/tools/nodetool/bootstrap.html  |   8 +-
 .../doc/trunk/cassandra/tools/nodetool/import.html |   6 +-
 .../trunk/cassandra/tools/nodetool/nodetool.html   |   9 +-
 .../cassandra/tools/nodetool/repair_admin.html     |  86 ++++++++--------
 content/search-index.js                            |   2 +-
 ...ssandra-4.0-users-unsplash-eden-constantino.jpg | Bin 0 -> 2324403 bytes
 .../modules/ROOT/images/companies/liquibase.svg    |   1 +
 site-content/source/modules/ROOT/pages/blog.adoc   |  25 +++++
 ...se-is-Ready-to-Support-Cassandra-4.0-Users.adoc |  18 ++++
 .../source/modules/ROOT/pages/case-studies.adoc    |  23 +++++
 .../modules/ROOT/pages/case-studies/Liquibase.adoc |  48 +++++++++
 site-ui/build/ui-bundle.zip                        | Bin 4740078 -> 4740078 
bytes
 26 files changed, 387 insertions(+), 261 deletions(-)
 create mode 100644 
content/_/_images/blog/liquibase-is-ready-to-support-cassandra-4.0-users-unsplash-eden-constantino.jpg
 create mode 100644 content/_/_images/companies/liquibase.svg
 copy content/_/blog/{Upgrade-Advisory2.html => 
Liquibase-is-Ready-to-Support-Cassandra-4.0-Users.html} (86%)
 copy content/_/{blog/ApacheCon-NA-2022-Call-for-Papers-Open.html => 
case-studies/Liquibase.html} (70%)
 create mode 100644 
site-content/source/modules/ROOT/images/blog/liquibase-is-ready-to-support-cassandra-4.0-users-unsplash-eden-constantino.jpg
 create mode 100644 
site-content/source/modules/ROOT/images/companies/liquibase.svg
 create mode 100644 
site-content/source/modules/ROOT/pages/blog/Liquibase-is-Ready-to-Support-Cassandra-4.0-Users.adoc
 create mode 100644 
site-content/source/modules/ROOT/pages/case-studies/Liquibase.adoc


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to