This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/celeborn-website.git
discard cbf87193 Deployed 9c53c77 with MkDocs version: 1.4.2
discard 3b210aae .asf.yaml
discard a6339b20 docs/0.4.1
discard e98bfb01 docs/0.4.0-incubating
discard 5476b279 docs/0.3.2-incubating
discard bcc9d8d3 docs/0.2.1-incubating
discard 3ddb026c docs/latest
discard 8ee7d513 .github/bin/build_docs.sh
discard 322641ee gitignore
discard 85187146 Deployed 7affbde with MkDocs version: 1.4.2
new b47e6d9e Deployed 9c53c77 with MkDocs version: 1.4.2
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 (cbf87193)
\
N -- N -- N refs/heads/asf-site (b47e6d9e)
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:
assets/logo/users/bytedance.png | Bin 258822 -> 0 bytes
assets/logo/users/qifu.png | Bin 153830 -> 0 bytes
sitemap.xml | 50 ++++++++++++++++++++--------------------
sitemap.xml.gz | Bin 215 -> 214 bytes
user/index.html | 6 -----
5 files changed, 25 insertions(+), 31 deletions(-)
delete mode 100644 assets/logo/users/bytedance.png
delete mode 100644 assets/logo/users/qifu.png
