commit-hurd
[Top][All Lists]
Advanced

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

[SCM] the great next stuff branch, dde, updated. a960afb9aae5a5160386d80


From: Justus Winter
Subject: [SCM] the great next stuff branch, dde, updated. a960afb9aae5a5160386d80a848c21bda788331a
Date: Tue, 29 Sep 2015 09:58:56 +0000

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 "the great next stuff".

The branch, dde has been updated
       via  a960afb9aae5a5160386d80a848c21bda788331a (commit)
       via  a29d8283c74c29d1b1ad978bd054c8171a465a98 (commit)
       via  bf2bad0a2a98ac983240c6ca8bb205f6b7e937ee (commit)
      from  b3c7fd96662643304b57eecdc0d0b9da1f4d3060 (commit)

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 a960afb9aae5a5160386d80a848c21bda788331a
Author: Justus Winter <address@hidden>
Date:   Mon Sep 28 15:24:00 2015 +0200

    libmachdev: convert to trivfs dynamic classes and buckets
    
    libtrivfs contains two ways of managing more than one port class and
    bucket.  There is the old way of using a statically allocated array
    with explicit length, and the new way with dynamically allocated
    vectors.
    
    Converting all users to the new way of handling multiple classes
    and/or buckets, we can simplify the code in libtrivfs.  In many cases,
    the code will be simpler and more expressive for the user.
    
    This also fixes a mild bug.  The classes and buckets given to
    `trivfs_startup' end up in the dynamic vectors too, making the object
    lookup code use the more complicated code path.
    
    * libmachdev/trivfs_server.c: Convert to dynamic classes and buckets.

commit a29d8283c74c29d1b1ad978bd054c8171a465a98
Author: Justus Winter <address@hidden>
Date:   Mon Sep 28 15:23:31 2015 +0200

    eth-filter: convert to trivfs dynamic classes and buckets
    
    libtrivfs contains two ways of managing more than one port class and
    bucket.  There is the old way of using a statically allocated array
    with explicit length, and the new way with dynamically allocated
    vectors.
    
    Converting all users to the new way of handling multiple classes
    and/or buckets, we can simplify the code in libtrivfs.  In many cases,
    the code will be simpler and more expressive for the user.
    
    This also fixes a mild bug.  The classes and buckets given to
    `trivfs_startup' end up in the dynamic vectors too, making the object
    lookup code use the more complicated code path.
    
    * eth-filter/filter.c: Convert to dynamic classes and buckets.

commit bf2bad0a2a98ac983240c6ca8bb205f6b7e937ee
Author: Justus Winter <address@hidden>
Date:   Mon Sep 28 15:22:29 2015 +0200

    devnode: convert to trivfs dynamic classes and buckets
    
    libtrivfs contains two ways of managing more than one port class and
    bucket.  There is the old way of using a statically allocated array
    with explicit length, and the new way with dynamically allocated
    vectors.
    
    Converting all users to the new way of handling multiple classes
    and/or buckets, we can simplify the code in libtrivfs.  In many cases,
    the code will be simpler and more expressive for the user.
    
    This also fixes a mild bug.  The classes and buckets given to
    `trivfs_startup' end up in the dynamic vectors too, making the object
    lookup code use the more complicated code path.
    
    * devnode/devnode.c: Convert to dynamic classes and buckets.

-----------------------------------------------------------------------

Summary of changes:
 devnode/devnode.c          |   27 +++++++++++++--------------
 eth-filter/filter.c        |   30 +++++++++++++++---------------
 libmachdev/trivfs_server.c |   29 ++++++++++++++---------------
 3 files changed, 42 insertions(+), 44 deletions(-)


hooks/post-receive
-- 
the great next stuff



reply via email to

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