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 "UNNAMED PROJECT".
The branch, laforge/gsmtap-category has been created
at 717cdf540558b95f31e4c8ea58d0fc9e06429228 (commit)
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-pcu/commit/?id=717cdf540558b95f31e4c8ea58d0fc9e06429228
commit 717cdf540558b95f31e4c8ea58d0fc9e06429228
Author: Harald Welte <[email protected]>
Date: Fri Jul 21 21:56:23 2017 +0200
Introduce GSMTAP categories
When looking at GSMTAP output so far, one is easily overwhelmed by way
too much information being presented. A lot of is consists of DUMMY
frames, which are probably of lowest interest, ever.
A concept similar to the "gsmtap-sapi" of OsmoBTS is introduced, by
which the user can configure which particular categories (uplink or
downlink control or data, gprs or egprs, ...) he actually wants to
see in his logs.
Change-Id: I297183690e98a7234dfc1608c18847d8981306e4
-----------------------------------------------------------------------
hooks/post-receive
--
UNNAMED PROJECT
