This is an automated email from the ASF dual-hosted git repository.
udim pushed a change to branch release-2.18.0
in repository https://gitbox.apache.org/repos/asf/beam.git.
omit 613b4bf Merge pull request #10302: [BEAM-4287] Fix to use the
residual instead of the current restriction on process continuations.
omit 96053a1 [Gradle Release Plugin] - new version commit:
'v2.18.0-SNAPSHOT'.
omit 50ba605 [Gradle Release Plugin] - pre tag commit: 'v2.18.0-RC1'.
omit 11f05b6 [BEAM-4287] Fix to use the residual instead of the current
restriction on process continuations.
new 9e58be1 [BEAM-4287] Fix to use the residual instead of the current
restriction on process continuations.
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 (613b4bf)
\
N -- N -- N refs/heads/release-2.18.0 (9e58be1)
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:
