[Top][All Lists]

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

[Viuavm-commits] [SCM] Viua VM branch issue-6329ca01-implement-i-o-instr

From: git
Subject: [Viuavm-commits] [SCM] Viua VM branch issue-6329ca01-implement-i-o-instructions updated. v0.9.0-2529-gfe221bf
Date: Sun, 1 Sep 2019 02:18:32 +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-6329ca01-implement-i-o-instructions has been updated
  discards  e94080fad55d70d36db9a6edfa747f8bb8608534 (commit)
  discards  17d68c1147b301a02a9763eb622197667c7a1f65 (commit)
       via  fe221bf4aadbae703588ae74d1723e1dba19936a (commit)
       via  908f5dca05f839c1a6d9274250f77430754709a8 (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 (e94080fad55d70d36db9a6edfa747f8bb8608534)
             N -- N -- N (fe221bf4aadbae703588ae74d1723e1dba19936a)

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 fe221bf4aadbae703588ae74d1723e1dba19936a
Author: Marek Marecki <address@hidden>
Date:   Sat Aug 31 21:40:02 2019 +0200

    Fix io_write
    It is now able to use IO_fd values passed as ports instead of just raw

commit 908f5dca05f839c1a6d9274250f77430754709a8
Author: Marek Marecki <address@hidden>
Date:   Sat Aug 31 21:39:33 2019 +0200

    IO_fd may own the file descriptor or may have just borrowed it
    It "owns" the file descriptor if it was used to create it. Owning IO_fd
    is responsible for proper shutdown of the file descriptor when the port
    goes out of scope.
    It "borrows" the file descriptor when it is used as a wrapper for a raw
    integer representing one. Borrowing IO_fd is not responsible for the
    shutdown of the file descriptor borrowed and is only used as a wrapper
    providing I/O interactions.


Summary of changes:

Viua VM

reply via email to

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