This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch juerg/remote-cache
in repository https://gitbox.apache.org/repos/asf/buildstream.git.
discard 046955d _stream.py: Parallelize cache queries if a remote cache is
configured
discard 8d27636 _scheduler: Add CacheQueryQueue to support cache query in job
threads
discard afdf70c _sandboxremote.py: Make storage-service optional with remote
cache
discard e0b99e3 _context.py: Add support for remote-cache configuration
add 025a282 _context.py: Add support for remote-cache configuration
add 1f2d61c _sandboxremote.py: Make storage-service optional with remote
cache
add 1cd174a _scheduler: Add CacheQueryQueue to support cache query in job
threads
add 4d95135 _stream.py: Parallelize cache queries if a remote cache is
configured
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 (046955d)
\
N -- N -- N refs/heads/juerg/remote-cache (4d95135)
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:
src/buildstream/_context.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
