Add missing opening <varlistentry> tag in the user manual.
PATCH 1/1 Add missing opening <varlistentry> tag in the user manual.
While we're here, remove the straggling hard-tabs.
Signed-off-by Jacob Helwig <[email protected]>
---
I hope this is the right way to submit a documentation fix. If not, please point me at the FM, since I didn't find it in looking through the Wiki, or the repo.
docs/usermanual/reference/var_src_uri.xml | 7 ++++--- 1 files changed, 4 insertions(+), 3 deletions(-)
docs/usermanual/reference/var_src_uri.xml +4 -3
@@ -455,11 +455,12 @@ SRC_URI[sha256sum] = "36bdb85c97b39ac604bc58cb7857ee08295242c78a12848ef8a31 </listitem> </varlistentry> + <varlistentry> <term>tag</term> <listitem> <para>The git tag to retrieve. The default is - <command>"master"</command>. This may be placed into + <command>"master"</command>. This may be placed into <command>SRCREV</command> instead.</para> </listitem> </varlistentry>
@@ -470,7 +471,7 @@ SRC_URI[sha256sum] = "36bdb85c97b39ac604bc58cb7857ee08295242c78a12848ef8a31 <listitem> <para>The method to use to access the repository. Common options are <command>"git"</command>, <command>"http"</command> and - <command>"rsync"</command>. The default is + <command>"rsync"</command>. The default is <command>"rsync"</command>.</para> </listitem> </varlistentry>
@@ -484,7 +485,7 @@ SRC_URI[sha256sum] = "36bdb85c97b39ac604bc58cb7857ee08295242c78a12848ef8a31 <listitem> <para>The revision of the git source to be checked out. - The default is <command>1</command> which is invalid and leads to + The default is <command>1</command> which is invalid and leads to an error.</para> </listitem> </varlistentry>
Signature · 1 line
1.7.0.4
Stefan Schmidt
AppliedHello.
Quoted 3 lines · Jacob Helwig
While we're here, remove the straggling hard-tabs.
Signed-off-by Jacob Helwig <[email protected]>
I applied and pushed this. Thanks for your contribution.
Quoted 5 lines
---
I hope this is the right way to submit a documentation fix. If not, please point me at the FM, since I didn't find it in looking through the Wiki, or the repo.
Thats the right way. I just added a "usermanual" prefix to your patch subject line to make it more clear for people what part of our repo it changes when browsing git log.
regards
Stefan Schmidt