This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch abderrahim/digest-environment
in repository https://gitbox.apache.org/repos/asf/buildstream.git
omit 97edc8564 tests/integration: Add tests for `digest-environment`
omit 2b47f5637 buildelement.py: Document `digest-environment`
omit 02f34dbe4 buildelement.py: Add the digest-environment config property
omit 46b1cc3d8 element.py: Don't call `configure_sandbox()` for non-build
sandboxes
omit ad3b98a70 Store sandbox state in Artifact proto
add 7e884747f Store sandbox state in Artifact proto
add 425c65315 buildelement.py: Add the digest-environment config property
add 958842582 buildelement.py: Document `digest-environment`
add a2f076f98 tests/integration: Add tests for `digest-environment`
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 (97edc8564)
\
N -- N -- N refs/heads/abderrahim/digest-environment (a2f076f98)
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/buildelement.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
