This is an automated email from the ASF dual-hosted git repository.
janardhan pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/systemds-website.git
discard da2f7f83 [MINOR] Fix Committers Pictures (#150)
omit 0a8a9edc add release notes, update docs
omit df602b44 remove profile in publish section
omit 8b8783e0 [DOCS] add documentation for 3.3.0
omit bf978305 [SYSTEMDS-3825] Remove Google Analytics from Old Docs
omit 8003cd1d [MINOR] update contributors (#143)
add 4e98e32b [MINOR] update contributors (#143) (#144)
add d92fd24a [SYSTEMDS-3825] Remove Google Analytics from Old Docs
add fca0990a [DOCS] add documentation for 3.3.0
add 29137290 remove profile in publish section
add fa3ce121 add release notes, update docs
add f1c1c598 [MINOR] Fix Committers Pictures (#150)
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 (da2f7f83)
\
N -- N -- N refs/heads/asf-staging (f1c1c598)
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.
No new revisions were added by this update.
Summary of changes:
