From: Pingfang Liao <pingfang.liao@outlook.com>
To: isar-users@googlegroups.com
Cc: pingfang.liao@outlook.com
Subject: [PATCH] doc: Cover conf/multiconfig/<CONFIG>.conf with ``
Date: Tue, 25 Jan 2022 02:06:30 -0500 [thread overview]
Message-ID: <SG2PR01MB36768E927B996768A3408D86E75F9@SG2PR01MB3676.apcprd01.prod.exchangelabs.com> (raw)
With markdown parser,it will generate:
conf/multiconfig/<CONFIG>.conf ==to==> conf/multiconfig/.conf
So it's better to cover conf/multiconfig/<CONFIG>.conf with ``.
Signed-off-by: Pingfang Liao <pingfang.liao@outlook.com>
---
doc/user_manual.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/user_manual.md b/doc/user_manual.md
index 535d456..ce3bf39 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -401,7 +401,7 @@ If BitBake is called with multiconfig targets (e.g.,
all supported configurations:
- `BBMULTICONFIG` - The list of the complete configuration definition files.
- BitBake looks for conf/multiconfig/<CONFIG>.conf in every layer. Every
+ BitBake looks for `conf/multiconfig/<CONFIG>.conf` in every layer. Every
configuration must define `MACHINE`, `DISTRO` and `DISTRO_ARCH`.
Some other variables include:
--
2.20.1
next reply other threads:[~2022-01-25 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 7:06 Pingfang Liao [this message]
2022-02-14 10:19 ` Anton Mikanovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SG2PR01MB36768E927B996768A3408D86E75F9@SG2PR01MB3676.apcprd01.prod.exchangelabs.com \
--to=pingfang.liao@outlook.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox