[Top][All Lists]

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

[Viuavm-commits] [SCM] Viua VM branch devel updated. v0.9.0-2639-g93215c

From: git
Subject: [Viuavm-commits] [SCM] Viua VM branch devel updated. v0.9.0-2639-g93215cc
Date: Thu, 26 Mar 2020 08:55:45 +0100 (CET)

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, devel has been updated
  discards  b38ebb194f211251e930c070072dd565940a82fb (commit)
  discards  53e7fc5d243432033d9c30c1f0315f5723652f99 (commit)
       via  93215cc9aaf33f8c522ea751e1d72d16ce78113b (commit)
       via  803c4af7997772587b5b09e7be1a2d38ee1e0a24 (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 (b38ebb194f211251e930c070072dd565940a82fb)
             N -- N -- N (93215cc9aaf33f8c522ea751e1d72d16ce78113b)

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 93215cc9aaf33f8c522ea751e1d72d16ce78113b
Author: Marek Marecki <address@hidden>
Date:   Thu Mar 26 08:52:19 2020 +0100

    Move register index type to codec

commit 803c4af7997772587b5b09e7be1a2d38ee1e0a24
Author: Marek Marecki <address@hidden>
Date:   Thu Mar 26 08:40:45 2020 +0100

    Use uint8_t instead of our custom byte type
    There is no use in typedefing that.


Summary of changes:

Viua VM

reply via email to

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