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 "An utility library for Open Source Mobile Communications".

The branch, master has been updated via dc75b114b4caf2692b145b7b254e2f6cfa627831 (commit) via a73656501a21c42223abdecc4c5df7bbe62c802c (commit) via 3b6815715f119e7c12c710deda6bc57738d46e37 (commit) via 453e37e3c8322cd200a6f803579c55753e866c7f (commit) via f7162771d78efb2d9d81caae0b10801771a39645 (commit) via 69054e28adf4c76371b82a34588e07211d264966 (commit) from 53aa0f51b8fffbaaa994b048fd18b63473bf4a79 (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 ----------------------------------------------------------------- http://cgit.osmocom.org/libosmocore/commit/?id=dc75b114b4caf2692b145b7b254e2...

commit dc75b114b4caf2692b145b7b254e2f6cfa627831 Author: Neels Hofmeyr neels@hofmeyr.de Date: Sat Dec 9 05:51:42 2017 +0100

comment: utils: more accurately describe OSMO_STRINGIFY macro

Change-Id: I7b057c026f9df90608b7cbd12481ab9e7a41d88c

http://cgit.osmocom.org/libosmocore/commit/?id=a73656501a21c42223abdecc4c5df...

commit a73656501a21c42223abdecc4c5df7bbe62c802c Author: Neels Hofmeyr neels@hofmeyr.de Date: Sat Dec 9 05:48:43 2017 +0100

vty reference: merge_doc.xsl: do not omit description tag

vty_additions.xml files provide <description>s for <node> tags, but for unknown reasons, merge_doc.xsl explicitly omits description tags. Do not omit <description>s so that they show up in the merged document.

This will take effect when next building the osmo-gsm-manuals using this file.

Change-Id: I418e61705043d4df047d8038c5d61623ba64f2e0

http://cgit.osmocom.org/libosmocore/commit/?id=3b6815715f119e7c12c710deda6bc...

commit 3b6815715f119e7c12c710deda6bc57738d46e37 Author: Neels Hofmeyr neels@hofmeyr.de Date: Sat Dec 9 03:54:32 2017 +0100

vty: set name for VIEW+ENABLE nodes, for VTY reference

This leaves no unnamed chapters in future VTY reference documents.

Change-Id: Iefb8b78094208a1a4c5d70bd6c69a3deca8da54f

http://cgit.osmocom.org/libosmocore/commit/?id=453e37e3c8322cd200a6f803579c5...

commit 453e37e3c8322cd200a6f803579c55753e866c7f Author: Neels Hofmeyr neels@hofmeyr.de Date: Sun Oct 22 02:31:33 2017 +0200

VTY reference: use node names as section names

In 'show online-help' output, add the node names (currently all derived from the prompt) as <node><name> entry, so that in the osmo-gsm-manuals, each section of node commands gets a title. So far, each section of commands has no name at all, and it is entirely up for guessing which part of the VTY the commands are about.

Node section names, e.g. for OsmoHLR, will be like

1 VTY reference 1.4 config 1.5 config-log 1.6 config-line 1.7 config-ctrl 1.8 config-hlr 1.9 config-hlr-gsup

Before this patch, all but '1 VTY reference' were plain empty.

A better solution would be to list the actual command name that enters the node, and to nest the commands identically to VTY node nesting, but since this information is currently hidden in node command implementations, it is impossible to derive it. So we should actually make the VTY reflect the node nesting structure in its data model, which would resolve both the accurate node name problem as well as produce well-structured output to generate the VTY references from. This patch is a workaround for lack of a more profound fix of the VTY data model. At least it makes the VTY references' sections even remotely useful.

Change-Id: Iaf745b2ab3d9b02fc47025a0eba3beb711068bfe

http://cgit.osmocom.org/libosmocore/commit/?id=f7162771d78efb2d9d81caae0b108...

commit f7162771d78efb2d9d81caae0b10801771a39645 Author: Neels Hofmeyr neels@hofmeyr.de Date: Sun Oct 22 02:31:33 2017 +0200

VTY reference: do not list empty nodes

In 'show online-help' output, don't list nodes that have no commands (the 'Password' node).

Change-Id: I3bd6883a87b8b893e560ceadfffbf41bc380109c

http://cgit.osmocom.org/libosmocore/commit/?id=69054e28adf4c76371b82a34588e0...

commit 69054e28adf4c76371b82a34588e07211d264966 Author: Neels Hofmeyr neels@hofmeyr.de Date: Thu Oct 19 02:44:57 2017 +0200

vty XML export: avoid repeating common node commands for each node

We use 'show online-help' to generate VTY reference manuals. It is not helpful to include the common node commands on each and every node level, it clutters the actual useful help.

Have a separate first section called 'Common Commands', but omit them elsewhere.

Change-Id: Ie802eccad80887968b10269ff9c0e9797268e0d4

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

Summary of changes: doc/vty/merge_doc.xsl | 4 +--- include/osmocom/core/utils.h | 4 +++- src/vty/command.c | 52 ++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 56 insertions(+), 4 deletions(-)

hooks/post-receive