From: joerg.sommer@navimatix.de
To: docs@lists.yoctoproject.org
Cc: "Jörg Sommer" <joerg.sommer@navimatix.de>
Subject: [PATCH] kernel-dev: join mkdir commands with -p
Date: Fri, 5 Apr 2024 12:14:20 +0200 [thread overview]
Message-ID: <31036f61cb79b07a4e774d799ec7bb8cf0bdbf07.1712312060.git.joerg.sommer@navimatix.de> (raw)
From: Jörg Sommer <joerg.sommer@navimatix.de>
To make it more obvious which directories are needed, pass only these to
*mkdir* and use the option `-p` to create the missing parents.
Signed-off-by: Jörg Sommer <joerg.sommer@navimatix.de>
---
documentation/kernel-dev/common.rst | 10 ++--------
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/documentation/kernel-dev/common.rst b/documentation/kernel-dev/common.rst
index 0cee503346..9a7a1907f6 100644
--- a/documentation/kernel-dev/common.rst
+++ b/documentation/kernel-dev/common.rst
@@ -315,11 +315,7 @@ home directory:
#. *Create Structure*: Create the layer's structure::
- $ mkdir meta-mylayer
- $ mkdir meta-mylayer/conf
- $ mkdir meta-mylayer/recipes-kernel
- $ mkdir meta-mylayer/recipes-kernel/linux
- $ mkdir meta-mylayer/recipes-kernel/linux/linux-yocto
+ $ mkdir -p meta-mylayer/conf meta-mylayer/recipes-kernel/linux/linux-yocto
The ``conf`` directory holds your configuration files, while the
``recipes-kernel`` directory holds your append file and eventual
@@ -964,9 +960,7 @@ Section.
additional structure to your layer using the following commands::
$ cd ~/meta-mylayer
- $ mkdir recipes-kernel
- $ mkdir recipes-kernel/linux
- $ mkdir recipes-kernel/linux/linux-yocto
+ $ mkdir -p recipes-kernel recipes-kernel/linux/linux-yocto
Once you have created this
hierarchy in your layer, you can move the patch file using the
--
2.34.1
next reply other threads:[~2024-04-05 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 10:14 joerg.sommer [this message]
2024-04-08 7:07 ` [docs] [PATCH] kernel-dev: join mkdir commands with -p Michael Opdenacker
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=31036f61cb79b07a4e774d799ec7bb8cf0bdbf07.1712312060.git.joerg.sommer@navimatix.de \
--to=joerg.sommer@navimatix.de \
--cc=docs@lists.yoctoproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).