From a077050a72025bc21c73eeece03db9c0bd075c0f Mon Sep 17 00:00:00 2001 From: Stephen Finucane Date: Tue, 30 Oct 2018 22:01:53 +0000 Subject: docs: Fix design doc These items weren't really headers and shouldn't have been rendered as such. Signed-off-by: Stephen Finucane --- docs/usage/design.rst | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) (limited to 'docs/usage') 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. -- cgit v1.2.3