This is an automated email from the git hooks/post-receive script.
"Maxim Kuvyrkov pushed a change to branch sq in repository toolchain/bmk-scripts.
discards e3da884 run.sh: Cleanup tx1_32 installs the same way as others discards 9da1807 Add settings for SynQuacer discards 5088831 Rework installation procedure new 9a6cdc5 Rework installation procedure new b83a573 Add settings for SynQuacer new 9e76331 run.sh: Cleanup tx1_32 installs the same way as others
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 (e3da884) \ N -- N -- N refs/heads/sq (9e76331)
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: run.sh | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)