This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch jbilleter/nested-reapi
in repository https://gitbox.apache.org/repos/asf/buildstream.git
discard d8b5e5003 Enable local execution in buildbox-casd to support nested
execution
discard 820c8515c _context.py: Add `effective_build_max_jobs` helper
discard 842129e21 sandbox: Add support for `remote-apis-socket`
new 32d527f5f sandbox: Add support for `remote-apis-socket`
new 467030f65 _context.py: Add `effective_build_max_jobs` helper
new 403d580e2 Enable local execution in buildbox-casd to support nested
execution
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 (d8b5e5003)
\
N -- N -- N refs/heads/jbilleter/nested-reapi (403d580e2)
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.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
