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 7e70de8  NEWS: Document breaking change, removed support for 
deprecated RE config
 discard 14637c8  _remotespec.py: Moving RemoteSpec and RemoteExecutionSpec to 
its own file
 discard 2b33efd  element.py: Remove local __remote_execution_specs instance 
variable
     add fcb7c8b  Merge pull request #1452 from apache/tristan/yaml-fixes
     add b7565f3  element.py: Remove local __remote_execution_specs instance 
variable
     add 96b5f73  _remotespec.py: Moving RemoteSpec and RemoteExecutionSpec to 
its own file
     add 7114f52  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   (7e70de8)
            \
             N -- N -- N   refs/heads/tristan/refactor-remote-config (7114f52)

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:

Reply via email to