[MacPorts] DraftKeywordGuidelines modified

[MacPorts]

Page "DraftKeywordGuidelines" was changed by raimue at macports.org
Diff URL: <https://trac.macports.org/wiki/DraftKeywordGuidelines?action=diff&version=13>
Revision 13
Comment: Rearrange large table into lists
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: DraftKeywordGuidelines
=========================================================================
--- DraftKeywordGuidelines (version: 12)
+++ DraftKeywordGuidelines (version: 13)
@@ -2,13 +2,35 @@
 
 Trac can search the full text of tickets, so adding a keyword that already occurs in another field doesn't help for general searching. If we standardise the use of certain keywords, however, it could make finding certain specific types of ticket much easier. This, then, is a suggested list of keywords that we might like to standardise.
 
-||= '''Keyword''' =||= '''Meaning''' =||
-|| [query:status=!closed&keywords=~tiger tiger]\\leopard\\[query:status=!closed&keywords=~snowleopard snowleopard]\\lion\\[query:status=!closed&keywords=~mountainlion mountainlion]\\[query:status=!closed&keywords=~mavericks mavericks]\\[query:status=!closed&keywords=~yosemite yosemite] || The ticket is only applicable to the indicated OS release(s). ||
-|| [query:status=!closed&keywords=~i386 i386]\\[query:status=!closed&keywords=~x86_64 x86_64]\\[query:status=!closed&keywords=~powerpc powerpc] \\[query:status=!closed&keywords=~powerpc64 powerpc64] || The ticket is only applicable when using the indicated `build_arch`. ||
-|| [query:status=!closed&keywords=~LP64 LP64] || The ticket describes a problem caused by the size of variables of type int, long or pointers on a 64-bit arch. ||
-|| [query:status=!closed&keywords=~haspatch haspatch] || The ticket has a patchfile attached that may be ready to apply. ||
-|| [https://trac.macports.org/query?status=assigned&status=new&status=reopened&keywords=~haspatch+maintainer&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=port&order=priority haspatch maintainer] || The ticket has a patchfile attached that was approved or supplied by the port maintainer that may be ready to apply. ||
-|| [query:status=!closed&keywords=~tracemode tracemode] || The ticket is only applicable when running port in `trace mode` (-t). ||
+Tickets only applicable to the indicated OS release(s):
+
+  * [query:status=!closed&keywords=~tiger tiger]
+  * [query:status=!closed&keywords=~leopard leopard]
+  * [query:status=!closed&keywords=~snowleopard snowleopard]
+  * [query:status=!closed&keywords=~lion lion]
+  * [query:status=!closed&keywords=~mountainlion mountainlion]
+  * [query:status=!closed&keywords=~mavericks mavericks]
+  * [query:status=!closed&keywords=~yosemite yosemite]
+
+Tickets only applicable when using the indicated `build_arch`:
+
+  * [query:status=!closed&keywords=~i386 i386]
+  * [query:status=!closed&keywords=~x86_64 x86_64]
+  * [query:status=!closed&keywords=~powerpc powerpc]
+  * [query:status=!closed&keywords=~powerpc64 powerpc64]
+  * [query:status=!closed&keywords=~LP64 LP64] \\
+    The ticket describes a problem caused by the size of variables of type int, long or pointers on a 64-bit arch.
+
+Tickets only applicable with patches:
+
+  * [query:status=!closed&keywords=~haspatch haspatch] \\
+    The ticket has a patchfile attached that may be ready to apply.
+  * [query:"status=!closed&keywords=~haspatch maintainer" haspatch maintainer] \\
+    The ticket has a patchfile attached that was approved or supplied by the port maintainer that may be ready to apply.
+
+The ticket is only applicable when running port in `trace mode` (-t):
+
+  * [query:status=!closed&keywords=~tracemode tracemode]
 
 {{{
 #!comment
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://trac.macports.org/wiki/DraftKeywordGuidelines>
MacPorts <https://www.macports.org/>
Ports system for OS X

This is an automated message. Someone added your email address to be
notified of changes on 'DraftKeywordGuidelines' page.
If it was not you, please report to .