Ignore:
Timestamp:
10/10/2021 06:14:39 AM (3 years ago)
Author:
Pierre Labastie <pierre.labastie@…>
Branches:
11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
f934af8
Parents:
9e2ff85
Message:

Better tags for bridge-utils SERVICE

use <envar> for the variable alone and <code> for the command,
so that it renders the same as in the subsequent "cat".

File:
1 edited

Legend:

Unmodified
Added
Removed
  • networking/netprogs/bridgeutils.xml

    r9e2ff85 r78962e30  
    167167
    168168      <para>
    169         Other SERVICE combinations are possible, for example,
    170         <command>SERVICE="bridge dhcp"</command>.  In that case, the address
     169        Other <envar>SERVICE</envar> combinations are possible, for example,
     170        <code>SERVICE="bridge dhcp"</code>.  In that case, the address
    171171        parameters are not needed, but do not interfere if present. The
    172172        bridge service may also be used alone, but will require
Note: See TracChangeset for help on using the changeset viewer.