libosmo-sccp.git branch laforge/wip updated.

gitosis at gitosis at
Thu Jan 7 11:34:23 UTC 2016

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 "SCCP Library".

The branch, laforge/wip has been updated
  discards  04fd9fc31b0b8cda034cfb7be128a8ccf8399b54 (commit)
  discards  22d4c9fafbf04533897102a68d6eaa07e0e58f09 (commit)
  discards  c576a64efa7ccad8b099c4ca165b8b6b3078d7d5 (commit)
  discards  7444079afb4cf85bb82a906453bf77ffcb7d89bd (commit)
  discards  578824d22f7805cb9fe9fd3907bfcf1940b42878 (commit)
       via  7cbce1a08a0be6b6cbad71f23e5951022b5502ac (commit)
       via  6d9e1b450697becc21e9faa029a8fddde7f486d9 (commit)
       via  6f6874f48ed2c5ba29a01513d7a58172bcf51dcc (commit)
       via  702c5864d7de01dfbf36e3f2d3bc38fa461aa8ea (commit)
       via  11dc282e7639493679847aeedbdb94d47cb83cd7 (commit)
       via  f4402676f21a20b711d7bbad644b997f946d871e (commit)
       via  1b65a4ceeb61cf9e58b9132962ee956a6caf02cb (commit)
       via  de2606249d1f539233fc4a52ab2ed72d9e91780a (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 (04fd9fc31b0b8cda034cfb7be128a8ccf8399b54)
             N -- N -- N (7cbce1a08a0be6b6cbad71f23e5951022b5502ac)

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 7cbce1a08a0be6b6cbad71f23e5951022b5502ac
Author: Harald Welte <laforge at>
Date:   Mon Jan 4 12:35:49 2016 +0100

    HACK: start to handle SCTP notifications

commit 6d9e1b450697becc21e9faa029a8fddde7f486d9
Author: Harald Welte <laforge at>
Date:   Sat Dec 26 23:36:27 2015 +0100

    sua: Ensure that a SUA client will continuously try to reconnect

commit 6f6874f48ed2c5ba29a01513d7a58172bcf51dcc
Author: Harald Welte <laforge at>
Date:   Sat Dec 26 23:35:31 2015 +0100

    sua: call conn_disconnect() in sua_disconnect_req()
    disconnect is not a class3/4 operation. We simply generate + send the
    DISCONNECT.ind message to the remote side and drop all local state about the

commit 702c5864d7de01dfbf36e3f2d3bc38fa461aa8ea
Author: Harald Welte <laforge at>
Date:   Sat Dec 26 23:34:54 2015 +0100

    sua: Fix typo in log message

commit 11dc282e7639493679847aeedbdb94d47cb83cd7
Author: Harald Welte <laforge at>
Date:   Sat Dec 26 23:34:03 2015 +0100

    allow user to give private data to osmo_sua_user_create()
    ... which can be resolved from the prim_cb() by calling


Summary of changes:              | 2 +-
 tests/m2ua/m2ua_test.c    | 4 ++--
 tests/sigtran/ | 1 +
 3 files changed, 4 insertions(+), 3 deletions(-)

SCCP Library

More information about the osmocom-commitlog mailing list