[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Viuavm-commits] [SCM] Viua VM branch issue/ce6f5d82/rewrite-assembler u

From: git
Subject: [Viuavm-commits] [SCM] Viua VM branch issue/ce6f5d82/rewrite-assembler updated. v0.9.0-2194-g037c6c0
Date: Fri, 5 Oct 2018 18:07:22 +0200 (CEST)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Viua VM".

The branch, issue/ce6f5d82/rewrite-assembler has been updated
  discards  71655b8701e512322f0737effa8b7047c75693a3 (commit)
       via  037c6c0058c8e103953b99ffc4ccf6dc9f8c4585 (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (71655b8701e512322f0737effa8b7047c75693a3)
             N -- N -- N (037c6c0058c8e103953b99ffc4ccf6dc9f8c4585)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 037c6c0058c8e103953b99ffc4ccf6dc9f8c4585
Author: Marek Marecki <address@hidden>
Date:   Fri Oct 5 18:06:45 2018 +0200



Summary of changes:
 src/tooling/libs/static_analyser/static_analyser.cpp | 13 +++++++++++++
 1 file changed, 13 insertions(+)

Viua VM

reply via email to

[Prev in Thread] Current Thread [Next in Thread]