This is an automated email from the git hooks/post-receive script.
bernie.ogden pushed a change to branch inserted_src in repository toolchain/semiautobench.
discards 3ec438a Make value of empty YAML parameter explicit discards 735f332 Move env so I can see the effect of leaving things unspecified discards 579dfba Check out with -b if abe_branch given discards eb96dd9 Remove ABE_DIR variable new 0d5dbe1 Check out with -b if abe_branch given new 9ebefb4 Move env so I can see the effect of leaving things unspecified new d626d2f Make value of empty YAML parameter explicit
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 (3ec438a) \ N -- N -- N refs/heads/inserted_src (d626d2f)
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: invoke_session_debian | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)