From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: buildroot@buildroot.org
Cc: Marcus Folkesson <marcus.folkesson@gmail.com>
Subject: [Buildroot] [PATCH] package/makedevs: describe the recursive type in the README
Date: Tue, 6 Feb 2024 10:00:48 +0100 [thread overview]
Message-ID: <20240206090048.2214719-1-marcus.folkesson@gmail.com> (raw)
The recursive type is described everywhere else, so add it to
the README as well.
Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
---
package/makedevs/README | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/makedevs/README b/package/makedevs/README
index 70844bf802..6c583609a5 100644
--- a/package/makedevs/README
+++ b/package/makedevs/README
@@ -26,6 +26,7 @@ where name is the file name, type can be one of:
f: A regular file
d: Directory
+ r: Directory recursively
c: Character special device file
b: Block special device file
p: Fifo (named pipe)
--
2.43.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-02-06 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 9:00 Marcus Folkesson [this message]
2024-02-07 11:10 ` [Buildroot] [PATCH] package/makedevs: describe the recursive type in the README Yann E. MORIN
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=20240206090048.2214719-1-marcus.folkesson@gmail.com \
--to=marcus.folkesson@gmail.com \
--cc=buildroot@buildroot.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