summaryrefslogtreecommitdiffstats
path: root/doc/vty
Commit message (Collapse)AuthorAgeFilesLines
* vty reference: merge_doc.xsl: do not omit description tagNeels Hofmeyr2017-12-101-3/+1
| | | | | | | | | | 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
* merge_doc.xsl: Don't copy the 'descripiton' element of commandsHarald Welte2016-03-111-1/+3
| | | | | | | If a vty_additions.xml file contained a <description> element inside a command> element, then the description was copied twice (once during the <node> copy, and once during the <command> copy). Let's avoid one of the two copies.
* vty: Merge from a generic section in case no specific one existsHolger Hans Peter Freyther2012-07-251-2/+11
|
* vty: Use UTF-8 for the encoding and the ability to hide nodesHolger Hans Peter Freyther2012-07-251-9/+11
| | | | | There are certain nodes one might not want to document and the additional information can decide to hide the node.
* vty: Add xsd and a command that can generate the documentation.Holger Hans Peter Freyther2012-07-253-0/+105
When building the doxygen documentation do not remove the other VTY documentation files in the doc/vty folder. Create a command that can be installed to dump all nodes and commands as XML on the given VTY. Create a schema for the XML file and a XSL-T script that can merge the generated file with additional information.