libosmocore.git branch neels/vty updated. 0.9.6-440-g2f5da1de

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.

gitosis at osmocom.org gitosis at osmocom.org
Sun Oct 22 00:45:20 UTC 2017


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, neels/vty has been updated
  discards  139d0c08d3e1dcf206f6fdcc04fbb53db777aff4 (commit)
  discards  b4e165914e3ed459b5dd7d6c5efb5803511a8a26 (commit)
  discards  6fa35b39e8b515e45689235cd7e7f40ae78b0ea8 (commit)
  discards  e8c9c0dc78035e2a085ef1d263486ed795eda8c5 (commit)
  discards  032846ad92776004faedca7be378f558234fec29 (commit)
       via  2f5da1de44f3bc54bd6267edb00634fd8ea7481e (commit)
       via  5e8c555b5f08f13fb2a3fc2180600aef465d73aa (commit)
       via  cb67201a62e7848538132d38020adab3acfdd1eb (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 (139d0c08d3e1dcf206f6fdcc04fbb53db777aff4)
            \
             N -- N -- N (2f5da1de44f3bc54bd6267edb00634fd8ea7481e)

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/libosmocore/commit/?id=2f5da1de44f3bc54bd6267edb00634fd8ea7481e

commit 2f5da1de44f3bc54bd6267edb00634fd8ea7481e
Author: Neels Hofmeyr <neels at 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=5e8c555b5f08f13fb2a3fc2180600aef465d73aa

commit 5e8c555b5f08f13fb2a3fc2180600aef465d73aa
Author: Neels Hofmeyr <neels at 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: Iaf745b2ab3d9b02fc47025a0eba3beb711068bfe

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

commit cb67201a62e7848538132d38020adab3acfdd1eb
Author: Neels Hofmeyr <neels at 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:
 include/osmocom/core/utils.h       | 18 ---------
 include/osmocom/ctrl/control_cmd.h |  3 --
 include/osmocom/ctrl/control_if.h  |  8 ----
 src/ctrl/control_if.c              | 81 +++++++-------------------------------
 4 files changed, 14 insertions(+), 96 deletions(-)


hooks/post-receive
-- 
An utility library for Open Source Mobile Communications



More information about the osmocom-commitlog mailing list