This is an automated email from the git hooks/post-receive script.
bernie.ogden pushed a change to branch bernie/benchmarking-uinstance in repository toolchain/abe.
discards 7cb245e Clean up path handling discards 3f34f82 WIP: Try collecting files sightly differently" discards 83b443f WIP: attach dir discards 9982639 WIP: Experiment in collecting metadata discards 2f47200 WIP: Attach individual files discards adc04b0 WIP: 'Semi-trusted' concept, for testing purposes discards c5b47c0 Add trusted-host-session.yaml new 3e4436b Attach raw files when gathering fakebench new fb3bfe5 Clean up path handling new f2de77c Add trusted-host-session.yaml new 0f8d3af WIP: 'Semi-trusted' concept, for testing purposes new e889867 WIP: Experiment in collecting metadata
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 (7cb245e) \ N -- N -- N refs/heads/bernie/benchmarking-uinstance (e889867)
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 "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 5 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: