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

mergebot-role pushed a change to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git.


 discard d23e1ba  This closes #388
 discard 4eae6c2  Explicitly define section id due to kramdown id generation 
changes
 discard e59956d  Update Gemfile.lock
     new 1a192bd  Update Gemfile.lock
     new 515cd4e  Explicitly define section id due to kramdown id generation 
changes
     new 6764c8c  This closes #388

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   (d23e1ba)
            \
             N -- N -- N   refs/heads/mergebot (6764c8c)

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 3 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:

-- 
To stop receiving notification emails like this one, please contact
mergebot-r...@apache.org.

Reply via email to