This is an automated email from the git hooks/post-receive script.
bernie.ogden pushed a change to branch bernie/fs in repository toolchain/abe.
discards b35ff38 Run second-stage for foreign chroots discards c104d6e Add check that HEAD maps to something meaningful upstream discards e5407da Introduce script to build filesystems adds db23354 Create a file to signal targets to end LAVA session new 16d7ac1 Introduce script to build filesystems new 55ab9a5 Add check that HEAD maps to something meaningful upstream new 7393af8 Run second-stage for foreign chroots
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 (b35ff38) \ N -- N -- N refs/heads/bernie/fs (7393af8)
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 3 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: config/bench/lava/host-session | 2 +- config/bench/lava/target-session | 5 ++++- config/bench/lava/target-session.yaml | 1 + 3 files changed, 6 insertions(+), 2 deletions(-)