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 854c33aa4 Enable local execution in buildbox-casd to support nested
execution
discard 9d856c578 _context.py: Add `effective_build_max_jobs` helper
discard 32d527f5f sandbox: Add support for `remote-apis-socket`
add f899c1479 Merge pull request #2013 from apache/jbilleter/reapi-platform
add ffec39552 sandbox: Add support for `remote-apis-socket`
add 45e3d60ff _context.py: Add `effective_build_max_jobs` helper
add a045d16b1 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 (854c33aa4)
\
N -- N -- N refs/heads/jbilleter/nested-reapi (a045d16b1)
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:
doc/source/format_declaring.rst | 18 ++++++++++++++++++
src/buildstream/sandbox/_config.py | 1 +
2 files changed, 19 insertions(+)
