This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch juerg/buildbox-asset-remote
in repository https://gitbox.apache.org/repos/asf/buildstream.git
discard 0cdb09663 _assetcache.py: Use buildbox-casd as remote asset proxy, if
supported
discard 975961acf _remotespec.py: Add `to_localcas_remote()` method
discard 3f9f213e5 Move `CASDProcessManager` instance from `CASCache` to
`Context`
add 22ee8a28f Move `CASDProcessManager` instance from `CASCache` to
`Context`
add fb0846170 _remotespec.py: Add `to_localcas_remote()` method
add cb0ccf64b _assetcache.py: Use buildbox-casd as remote asset proxy, if
supported
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 (0cdb09663)
\
N -- N -- N refs/heads/juerg/buildbox-asset-remote (cb0ccf64b)
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/internals/cascache.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
