This is an automated email from the ASF dual-hosted git repository.
tvb pushed a change to branch tristan/sboms
in repository https://gitbox.apache.org/repos/asf/buildstream.git
discard e551c426b frontend: Support %{source-info} in `bst show`
discard 21bec8461 local source: Implement collect_source_info()
discard 028ee1eb1 downloadablefilesource.py: Implement collect_source_info()
add 26ad0d5d9 downloadablefilesource.py: Implement collect_source_info()
add 60a7246bf local source: Implement collect_source_info()
add ea856b19d frontend: Support %{source-info} in `bst show`
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 (e551c426b)
\
N -- N -- N refs/heads/tristan/sboms (ea856b19d)
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/downloadablefilesource.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)