This is an automated email from the ASF dual-hosted git repository.

github-actions[bot] pushed a change to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/iceberg-cpp.git


 discard b67ea4d9 Publish docs from commit 
87a11de7e83785d925cf3dcc31d84100dccfb62f
     new 35dea864 Publish docs from commit 
587fb6989221631044942c621edcd6a810fd6b8c

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   (b67ea4d9)
            \
             N -- N -- N   refs/heads/gh-pages (35dea864)

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:
 api/search/all_12.js              |  12 ++++++------
 api/search/files_f.js             |   2 +-
 api/xml/index.xml                 |  12 ++++++------
 mkdocs/docs/api/search/all_12.js  |  12 ++++++------
 mkdocs/docs/api/search/files_f.js |   2 +-
 mkdocs/docs/api/xml/index.xml     |  12 ++++++------
 mkdocs/site/api/search/all_12.js  |  12 ++++++------
 mkdocs/site/api/search/files_f.js |   2 +-
 mkdocs/site/api/xml/index.xml     |  12 ++++++------
 mkdocs/site/sitemap.xml           |  14 +++++++-------
 mkdocs/site/sitemap.xml.gz        | Bin 251 -> 250 bytes
 sitemap.xml                       |  14 +++++++-------
 sitemap.xml.gz                    | Bin 251 -> 250 bytes
 13 files changed, 53 insertions(+), 53 deletions(-)

Reply via email to