This is an automated email from the git hooks/post-receive script.
"Diana Picus pushed a change to branch diana/docker-bmk%wip in repository toolchain/bmk-scripts.
discards 40bb46c run.sh: Use different SPEC install dir for AArch32 discards 9f44693 run.sh: Refactor ${installdir}. NFC adds 6862704 Fix prepare-board.sh --stop adds 59c4718 perfdatadir2csv.sh: Add workaround for perf-report issue new 95d29f1 run.sh: Refactor ${installdir}. NFC new a7cc6c4 run.sh: Use different SPEC install dir for AArch32
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 (40bb46c) \ N -- N -- N refs/heads/diana/docker-bmk%wip (a7cc6c4)
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 2 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: perfdatadir2csv.sh | 28 +++++++++++++++++++++++++--- run.sh | 2 +- 2 files changed, 26 insertions(+), 4 deletions(-)