commit:     5914e1444dccfb9229bd5f7973070dc825a621c8
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 15 07:20:25 2021 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Mon Feb 15 07:20:25 2021 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=5914e144

keywording: Fix coding style

Fixes: 9c2e6f500a276b974bc2e2bd476d8423f113dbb2
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 keywording/text.xml | 38 +++++++++++++++++++-------------------
 1 file changed, 19 insertions(+), 19 deletions(-)

diff --git a/keywording/text.xml b/keywording/text.xml
index b151e26..bf924af 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -334,25 +334,25 @@ So packages are not to be marked stable for one of these 
architectures.
 
 <subsection>
 <title>Simultaneous stabilization on all architectures</title>
-  <body>
-    <p>
-      If you maintain an architecture-independent package (data files,
-      icons, pure Perl,...) then you may request that your
-      package be stabilized on all arches at once. To do this <d/> when
-      you are filing the stabilization bug <d/> please add the keyword
-      <c>ALLARCHES</c> in addition to <c>STABLEREQ</c> and CC the
-      arches that you would like to stabilize.
-    </p>
-
-    <p>
-      The arch teams, when encountering the <c>ALLARCHES</c> keyword,
-      should perform their usual set of tests on a single convenient
-      architecture. Then, if everything works, stabilize not only the
-      arch that was used during testing, but also all of the other
-      arches in CC on the bug. Afterwards, the CC field can be cleared
-      and the bug closed if appropriate.
-    </p>
-  </body>
+<body>
+
+<p>
+If you maintain an architecture-independent package (data files, icons, pure
+Perl, ...) then you may request that your package be stabilized on all arches
+at once. To do this <d/> when you are filing the stabilization bug <d/> please
+add the keyword <c>ALLARCHES</c> in addition to <c>STABLEREQ</c> and CC the
+arches that you would like to stabilize.
+</p>
+
+<p>
+The arch teams, when encountering the <c>ALLARCHES</c> keyword, should perform
+their usual set of tests on a single convenient architecture. Then, if
+everything works, stabilize not only the arch that was used during testing,
+but also all of the other arches in CC on the bug. Afterwards, the CC field can
+be cleared and the bug closed if appropriate.
+</p>
+
+</body>
 </subsection>
 </section>
 

Reply via email to