Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: yann.morin@orange.com, Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] docs/manual: extend makedev syntax section
Date: Thu, 29 Feb 2024 16:46:54 +0100	[thread overview]
Message-ID: <87msrje0i9.fsf@48ers.dk> (raw)
In-Reply-To: <20240206115300.0bd8b584@windsurf> (Thomas Petazzoni via buildroot's message of "Tue, 6 Feb 2024 11:53:00 +0100")

>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:

 > On Thu, 18 Jan 2024 17:08:50 +0100
 > <yann.morin@orange.com> wrote:

 >> From: "Yann E. MORIN" <yann.morin@orange.com>
 >> 
 >> The section of the manual describing the makedev syntax is not
 >> up-to-date with the current features, and does not properly describe
 >> existing ones.
 >> 
 >> - extend the list of types with the requirements on the existence of
 >> the target file or directory; for 'c', 'b', and 'p', the existence
 >> requirement is inherited from mknod(2):
 >> 
 >> ERRORS
 >> ...
 >> ENOENT A directory component in pathname does not exist or is a
 >> dangling symbolic link.
 >> 
 >> for the other types, the existence requirements are extracted from
 >> the source of makedev.c;
 >> 
 >> - format the types fags, so they are rendered in monospace;
 >> 
 >> - extend the 'mode' description, as it can be set to -1 for 'f', 'd',
 >> or 'r', so that only the uid and gid are set. This is most useful
 >> for 'r', where setting the same mode recursively for all the
 >> sub-directories and files alike does not really make sense; indeed
 >> in this case, the modes are usually set correctly when the package
 >> (or rootfs overlay) installs the files, and only the uid and gid are
 >> interesting to set;
 >> 
 >> - extend and update the examples to show-case the -1 mode use-case.
 >> 
 >> Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
 >> ---
 >> docs/manual/makedev-syntax.adoc | 33 +++++++++++++++++++--------------
 >> 1 file changed, 19 insertions(+), 14 deletions(-)

 > Applied to master (with the typo in the commit log fixed), thanks!

Committed to 2023.02.x and 2023.11.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-02-29 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 16:08 [Buildroot] [PATCH] docs/manual: extend makedev syntax section yann.morin
2024-01-18 16:26 ` yann.morin
2024-02-06 10:53 ` Thomas Petazzoni via buildroot
2024-02-29 15:46   ` Peter Korsgaard [this message]

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=87msrje0i9.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin@orange.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