You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@calcite.apache.org by mm...@apache.org on 2020/01/22 01:19:54 UTC

[calcite] branch site updated (3ced74e -> e91059e)

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

mmior pushed a change to branch site
in repository https://gitbox.apache.org/repos/asf/calcite.git.


 discard 3ced74e  Site: Switch PMC Chair to Stamatis Zampetakis
 discard 99fba87  Site: Add Haisheng Yuan as PMC
 discard 317cc7f  Site: Append '(FirstName LastName)' to commit message example in contributing section
 discard 0f805bb  Site: Add Danny Chan as PMC
 discard 7020192  [CALCITE-3445] In web site, automatically redirect http to https
 discard 4c92f0d  [CALCITE-3391] Insecure pages warning on Chrome
 discard b593883  Site: Update upcoming talks section for ApacheCon Europe 2019
 discard 1c73a43  Site: Change GitHub avatar links to https
 discard 0efd728  Improve READMEs and release howto instructions
 discard 1027af7  Site: Add new committers: Julian Feinauer and Muhammad Gelbana
    omit 4ce87bb  Site: Add upcoming talks at ApacheCon NA 2019
     add 43cb194  Site: Add upcoming talks at ApacheCon NA 2019
     add 11e5dc2  Site: Add new committers: Julian Feinauer and Muhammad Gelbana
     add 0331a53  Improve READMEs and release howto instructions
     add 3fc3b71  Site: Change GitHub avatar links to https
     add 72ba84e  Site: Update upcoming talks section for ApacheCon Europe 2019
     add 5907379  [CALCITE-3391] Insecure pages warning on Chrome
     add 33d10a2  [CALCITE-3445] In web site, automatically redirect http to https
     add b385d7d  Site: Add Danny Chan as PMC
     add 08e3aea  Site: Append '(FirstName LastName)' to commit message example in contributing section
     add 76f40f2  Site: Add Haisheng Yuan as PMC
     add e91059e  Site: Switch PMC Chair to Stamatis Zampetakis

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   (3ced74e)
            \
             N -- N -- N   refs/heads/site (e91059e)

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: