This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch juerg/non-strict-cache-key
in repository https://gitbox.apache.org/repos/asf/buildstream.git.
discard 51b6fe1 element.py: Compute cache key also for rdep without buildable
callback
discard 772e786 element.py: Reorder checks in _buildable()
add 5e0bcc1 Only show the Initializing remote caches message once
add 7045bec Merge pull request #1451 from abderrahim/init-remote-caches
add 5f7165f element: batch integration command when running a shell
add bb59c70 Merge pull request #1435 from
abderrahim/batch-integration-commands
add 9c82bc8 element.py: Reorder checks in _buildable()
add 7b5a125 element.py: Compute cache key also for rdep without buildable
callback
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 (51b6fe1)
\
N -- N -- N refs/heads/juerg/non-strict-cache-key (7b5a125)
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/_assetcache.py | 25 ++++++++++++-------------
src/buildstream/_context.py | 7 ++++---
src/buildstream/element.py | 2 +-
3 files changed, 17 insertions(+), 17 deletions(-)
