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 "Osmocom network interface library".

The branch, stsp/destroy_conn_with_zero_msg has been updated
  discards  a19a53381fd769f82ec0f5a63db0b9fc2cd8aac4 (commit)
       via  76ead75d0a873e8a6170e336fc6b35dedb67b7dd (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 (a19a53381fd769f82ec0f5a63db0b9fc2cd8aac4)
             N -- N -- N (76ead75d0a873e8a6170e336fc6b35dedb67b7dd)

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 76ead75d0a873e8a6170e336fc6b35dedb67b7dd
Author: Stefan Sperling <>
Date:   Thu Feb 22 17:11:14 2018 +0100

    allow osmo_stream_srv_send() to destroy the connection
    If a zero-length message buffer is sent, destroy the corresponding
    Change-Id: I7e01fece294a77bf673c540f6c3310cff79da123


Summary of changes:

Osmocom network interface library

Reply via email to