This is an automated email from the ASF dual-hosted git repository.
pabloem pushed a change to branch release-2.6.0
in repository https://gitbox.apache.org/repos/asf/beam.git.
discard dd06e9a Use the same language semantics as defined by version of the
interpreter for Cythonizing. Use `past.builtins.basestring` consistently to
type-check strings.
omit 62a668f [Gradle Release Plugin] - pre tag commit: 'v2.6.0-RC2'.
omit 4fc6f99 [Gradle Release Plugin] - new version commit:
'v2.6.0-SNAPSHOT'.
omit 5b90329 [Gradle Release Plugin] - pre tag commit: 'v2.6.0-RC2'.
new 163e0f0 Use the same language semantics as defined by version of the
interpreter for Cythonizing. Use `past.builtins.basestring` consistently to
type-check strings.
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 (dd06e9a)
\
N -- N -- N refs/heads/release-2.6.0 (163e0f0)
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:
gradle.properties | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
