aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorStephen Finucane <stephen@that.guru>2018-10-30 22:01:53 +0000
committerStephen Finucane <stephen@that.guru>2018-10-30 22:05:58 +0000
commita077050a72025bc21c73eeece03db9c0bd075c0f (patch)
treec9cfcf7dcaecc5fa350916ce0a2b972238a500d3 /docs
parent5a69589ba82e81ced4366c591482fd303ec2f7aa (diff)
downloadpatchwork-a077050a72025bc21c73eeece03db9c0bd075c0f.tar
patchwork-a077050a72025bc21c73eeece03db9c0bd075c0f.tar.gz
docs: Fix design doc
These items weren't really headers and shouldn't have been rendered as such. Signed-off-by: Stephen Finucane <stephen@that.guru>
Diffstat (limited to 'docs')
-rw-r--r--docs/usage/design.rst9
1 files changed, 3 insertions, 6 deletions
diff --git a/docs/usage/design.rst b/docs/usage/design.rst
index 56719ee..9fc68b6 100644
--- a/docs/usage/design.rst
+++ b/docs/usage/design.rst
@@ -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.