[lxc-devel] [lxd/master] doc: tweak markdown format

tenforward on Github lxc-bot at linuxcontainers.org
Mon Feb 17 16:52:45 UTC 2020

A non-text attachment was scrubbed...
Name: not available
Type: text/x-mailbox
Size: 398 bytes
Desc: not available
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20200217/1ca771ec/attachment.bin>
-------------- next part --------------
From 18b4df801a55d4089c10e989410fe7efe5e8eb5c Mon Sep 17 00:00:00 2001
From: KATOH Yasufumi <karma at jazz.email.ne.jp>
Date: Tue, 18 Feb 2020 01:49:41 +0900
Subject: [PATCH] doc: tweak markdown format

We need linefeed to display as bullets.

Signed-off-by: KATOH Yasufumi <karma at jazz.email.ne.jp>
 doc/contributing.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/doc/contributing.md b/doc/contributing.md
index 2d1cc66a51..75aa7c88f9 100644
--- a/doc/contributing.md
+++ b/doc/contributing.md
@@ -8,6 +8,7 @@ be merged in the main branch.
 ## Commit structure
 Separate commits should be used for:
  - API extension (`api: Add XYZ extension`, contains `doc/api-extensions.md` and `shared/version.api.go`)
  - Documentation (`doc: Update XYZ` for files in `doc/`)
  - API structure (`shared/api: Add XYZ` for changes to `shared/api/`)
@@ -21,6 +22,7 @@ The same kind of pattern extends to the other tools in the LXD code tree
 and depending on complexity, things may be split into even smaller chunks.
 When updating strings in the CLI tool (`lxc/`), you may need a commit to update the templates:
  - make i18n
  - git commit -a -s -m "i18n: Update translation templates" po/

More information about the lxc-devel mailing list