libosmo-abis.git branch lynxis/unixsocket_version_header updated. 0.3.2-64-g0e677df

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 A-bis protcol interface library". The branch, lynxis/unixsocket_version_header has been updated discards 4188b811a6e90b99e78b7eecd9cc044dc0846f3f (commit) via 0e677dfc898f3b912f13fc46411a20303e1c2d11 (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 (4188b811a6e90b99e78b7eecd9cc044dc0846f3f) \ N -- N -- N (0e677dfc898f3b912f13fc46411a20303e1c2d11) 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 ----------------------------------------------------------------- http://cgit.osmocom.org/libosmo-abis/commit/?id=0e677dfc898f3b912f13fc46411… commit 0e677dfc898f3b912f13fc46411a20303e1c2d11 Author: Alexander Couzens <lynxis(a)fe80.eu> Date: Tue Feb 21 15:30:05 2017 +0100 unixsocket: introduce a version/datacontrol header (2byte) The ALT TC/Superchannel switch requires a seperate side channel. By introducing a header this can be done in a clean way. So every packet gets - 1 byte version - 1 byte data or control Change-Id: I0b601b67450b93291b2c2bcec5b0919050e18791 ----------------------------------------------------------------------- Summary of changes: src/input/unixsocket.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- Osmocom A-bis protcol interface library