File: refentry.xml

package info (click to toggle)
docbook-defguide 2.0.17%2Bsvn9912-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster
  • size: 93,432 kB
  • ctags: 299
  • sloc: xml: 396,482; perl: 4,471; python: 879; makefile: 150; sh: 80
file content (45 lines) | stat: -rw-r--r-- 1,138 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
<refentry id="revision.element">
<?dbhtml filename="revision.html"?>
<refentryinfo>
<pubdate>$Date$</pubdate>
<releaseinfo>$Revision$</releaseinfo>
</refentryinfo>

<refmeta>
<indexterm><primary>elements</primary>
<secondary>revision</secondary></indexterm>
<refentrytitle>revision</refentrytitle>
<refmiscinfo>Element</refmiscinfo>
</refmeta>
<refnamediv>
<refname>revision</refname>
<refpurpose>&revision.purpose;</refpurpose>
</refnamediv>

&revision.synopsis.gen;
<refsect1 condition='ref.description'><title>Description</title>

<para>
<sgmltag>Revision</sgmltag> contains information about a single revision to
a document.  Revisions are identified by a number and a date. They may
also include the initials of the author, and additional remarks.
</para>

<refsect2><title>Processing expectations</title>
<para>
<sgmltag>Revision</sgmltag>s are often presented in a list or table. In a
tabular presentation, each revision most likely forms a row in
the table.
</para>
</refsect2>


&revision.parents.gen;
&revision.children.gen;
</refsect1>
<refsect1><title>Examples</title>

&revision.example.seealso.gen;
</refsect1>
</refentry>