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 ec673ed8 generate docs for 11349c1a add b1be68c0 Update how_to_commit documentation with lost updates from in-tree repo new bc24893c generate docs for b1be68c0 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 (ec673ed8) \ N -- N -- N refs/heads/asf-staging (bc24893c) 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/_/development/how_to_commit.html | 317 ++++++++++++++++++--- content/_/development/index.html | 314 +++++++++++++++++--- content/search-index.js | 2 +- .../ROOT/pages/development/how_to_commit.adoc | 187 +++++++++--- site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes 5 files changed, 693 insertions(+), 127 deletions(-) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org