Docs: LCL/lclversion. Fixes tagging for See Also links.

This commit is contained in:
dsiders 2025-04-11 04:04:49 -04:00
parent 32186ee83e
commit 0e6bf19030

View File

@ -46,7 +46,9 @@ values, formatted with 2 digits and concatenated (leading zeros are omitted).
For example, if the LCL version is 2.2.4.1, lcl_fullversion will be 2020401. For example, if the LCL version is 2.2.4.1, lcl_fullversion will be 2020401.
</p> </p>
</descr> </descr>
<seealso>lcl_version</seealso> <seealso>
<link id="lcl_version"/>
</seealso>
</element> </element>
<element name="lcl_major"> <element name="lcl_major">
@ -80,7 +82,9 @@ Development (or trunk) versions are always represented as minor version number
selected commits from this branch are cherry picked to the 3.X family. selected commits from this branch are cherry picked to the 3.X family.
</p> </p>
</descr> </descr>
<seealso>lcl_version</seealso> <seealso>
<link id="lcl_version"/>
</seealso>
</element> </element>
<element name="lcl_release"> <element name="lcl_release">
@ -96,7 +100,9 @@ maintained and will always contain 0 (zero). Releases are represented using
the major and minor version numbers: 3.0, 3.1, 3.2, etc. the major and minor version numbers: 3.0, 3.1, 3.2, etc.
</p> </p>
</descr> </descr>
<seealso>lcl_version</seealso> <seealso>
<link id="lcl_version"/>
</seealso>
</element> </element>
<element name="lcl_patch"> <element name="lcl_patch">
@ -108,7 +114,9 @@ contains the last number (1). If there is no fourth number, for example when
the version string is 2.2.4, then lcl_patch is 0. the version string is 2.2.4, then lcl_patch is 0.
</p> </p>
</descr> </descr>
<seealso>lcl_version</seealso> <seealso>
<link id="lcl_version"/>
</seealso>
</element> </element>
<element name="lcl_version"> <element name="lcl_version">