]> git.ipfire.org Git - thirdparty/patchwork.git/commitdiff
docs: Fix design doc
authorStephen Finucane <stephen@that.guru>
Tue, 30 Oct 2018 22:01:53 +0000 (22:01 +0000)
committerStephen Finucane <stephen@that.guru>
Tue, 30 Oct 2018 22:05:58 +0000 (22:05 +0000)
These items weren't really headers and shouldn't have been rendered as
such.

Signed-off-by: Stephen Finucane <stephen@that.guru>
docs/usage/design.rst

index 56719eed4576fc4ed9dd71018553e7790e339ace..9fc68b61f273596f4f46ab96dbea224bd2b8b48d 100644 (file)
@@ -1,8 +1,7 @@
 Design
 ======
 
-Patchwork should supplement mailing lists, not replace them
------------------------------------------------------------
+**Patchwork should supplement mailing lists, not replace them**
 
 Patchwork isn't intended to replace a community mailing list; that's why you
 can't comment on a patch in Patchwork. If this were the case, then there would
@@ -10,14 +9,12 @@ be two forums of discussion on patches, which fragments the patch review
 process. Developers who don't use Patchwork would get left out of the
 discussion.
 
-Don't pollute the project's changelogs with Patchwork poop
-----------------------------------------------------------
+**Don't pollute the project's changelogs with Patchwork poop**
 
 A project's changelogs are valuable - we don't want to add Patchwork-specific
 metadata.
 
-Patchwork users shouldn't require a specific version control system
--------------------------------------------------------------------
+**Patchwork users shouldn't require a specific version control system**
 
 Not everyone uses git for kernel development, and not everyone uses git for
 Patchwork-tracked projects.