This is an automated email from the ASF dual-hosted git repository.
tvb pushed a change to branch tristan/refactor-remote-config
in repository https://gitbox.apache.org/repos/asf/buildstream.git.
discard 1bb0cd4 NEWS: Document breaking change, removed support for
deprecated RE config
discard 2cf7bc3 _remotespec.py: Moving RemoteSpec and RemoteExecutionSpec to
its own file
discard 248e71a element.py: Remove local __remote_execution_specs instance
variable
discard f957614 node.pyi: Adding some missing type annotations
add 8cbbeb1 .asf.yaml: Redirect notifications to the commit list
add fbe432f node.pyi: Adding some missing type annotations
add aed4108 element.py: Remove local __remote_execution_specs instance
variable
add 2979f7b _remotespec.py: Moving RemoteSpec and RemoteExecutionSpec to
its own file
add 00f91bc NEWS: Document breaking change, removed support for
deprecated RE config
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 (1bb0cd4)
\
N -- N -- N refs/heads/tristan/refactor-remote-config (00f91bc)
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:
.asf.yaml | 8 ++++++++
1 file changed, 8 insertions(+)
