From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 221686] New: README.d/ is not mentioned in README
Date: Wed, 24 Jun 2026 10:24:56 +0000 [thread overview]
Message-ID: <bug-221686-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221686
Bug ID: 221686
Summary: README.d/ is not mentioned in README
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: enhancement
Priority: P3
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: jason@jasonyundt.email
Regression: No
The README file for the Linux man-pages project has a section named “Files”
that lists a bunch of different files and directories and describes them. The
“Files” section mentions the CONTRIBUTING file, the CONTRIBUTING.d/ directory
and the README file, but it does not mention the README.d/ directory. It would
be better if the README mentioned the README.d/ directory.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2026-06-24 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 10:24 bugzilla-daemon [this message]
2026-06-24 10:43 ` [Bug 221686] README.d/ is not mentioned in README bugzilla-daemon
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=bug-221686-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.