This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch juerg/re-proxy
in repository https://gitbox.apache.org/repos/asf/buildstream.git
discard fade3c89c .github/common.env: Update CI images to use BuildBox 1.2.8
discard 3cbdb5e00 _sandboxremote.py: Use buildbox-casd as remote execution
proxy
add aec62cd58 _sandboxremote.py: Use buildbox-casd as remote execution
proxy
add b09952653 .github/common.env: Update CI images to use BuildBox 1.2.8
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 (fade3c89c)
\
N -- N -- N refs/heads/juerg/re-proxy (b09952653)
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:
tests/remotecache/simple.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
