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

goenka pushed a change to branch release-2.13.0
in repository https://gitbox.apache.org/repos/asf/beam.git.


    omit c6b0250  Merge pull request #8631 from udim/datastore-version-pip-check
    omit aa67310  [Gradle Release Plugin] - new version commit:  
'v2.13.0-SNAPSHOT'.
    omit 868db1c  [Gradle Release Plugin] - pre tag commit:  'v2.13.0-RC1'.
    omit 682144e  Merge pull request #8638: [release-2.13.0][BEAM-7230] Make 
PoolableDataSourceProvider a static singleton
     new 30a4089  Merge pull request #8631 from udim/datastore-version-pip-check
     new 01e252d  [Gradle Release Plugin] - pre tag commit:  'v2.13.0-RC1'.
     new ee91a25  [Gradle Release Plugin] - new version commit:  
'v2.13.0-SNAPSHOT'.

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   (c6b0250)
            \
             N -- N -- N   refs/heads/release-2.13.0 (ee91a25)

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:

Reply via email to