shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2025-01-11 05:17:44 +03:00
Code

man: use the same markup for "ap" everywhere

Browse Source
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2018-07-02 23:21:04 +02:00
parent 28c7474e60
commit c765233c89
2 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
man/sd_bus_error.xml
View File

@ -100,7 +100,7 @@
<paramdef>sd_bus_error *<parameter>e</parameter></paramdef> <paramdef>sd_bus_error *<parameter>e</parameter></paramdef>
<paramdef>int <parameter>error</parameter></paramdef> <paramdef>int <parameter>error</parameter></paramdef>
<paramdef>const char *<parameter>format</parameter></paramdef> <paramdef>const char *<parameter>format</parameter></paramdef>
<paramdef>va_list ap</paramdef> <paramdef>va_list <parameter>ap</parameter></paramdef>
</funcprototype> </funcprototype>
<funcprototype> <funcprototype>

13
man/sd_bus_message_append.xml
View File

@ -94,13 +94,12 @@
values for each entry matching the element type of values for each entry matching the element type of
the dictionary entries.</para> the dictionary entries.</para>
<para>The <function>sd_bus_message_appendv()</function> is equivalent to <para>The <function>sd_bus_message_appendv()</function> is equivalent to the
the function <function>sd_bus_message_append()</function>, <function>sd_bus_message_append()</function>, except that it is called with
except that it is called with a <literal>va_list</literal> instead of a <literal>va_list</literal> instead of a variable number of arguments. This
a variable number of arguments. This function does not call the function does not call the <function>va_end()</function> macro. Because it
<function>va_end()</function> macro. Because it invokes the invokes the <function>va_arg()</function> macro, the value of
<function>va_arg()</function> macro, the value of ap <parameter>ap</parameter> is undefined after the call.</para>
is undefined after the call.</para>
<para>For further details on the D-Bus type system, please consult <para>For further details on the D-Bus type system, please consult
the <ulink the <ulink