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 403d580e2 Enable local execution in buildbox-casd to support nested
execution
discard 467030f65 _context.py: Add `effective_build_max_jobs` helper
add 9d856c578 _context.py: Add `effective_build_max_jobs` helper
add 854c33aa4 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 (403d580e2)
\
N -- N -- N refs/heads/jbilleter/nested-reapi (854c33aa4)
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/_cas/casdprocessmanager.py | 2 +-
src/buildstream/_context.py | 8 ++------
2 files changed, 3 insertions(+), 7 deletions(-)
