From: Martin Wilck <mwilck@suse.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
DM-DEVEL ML <dm-devel@redhat.com>
Subject: Re: [dm-devel] [PATCH] multipath-tools: add basic info on how to use multipath-tools with NVMe devices
Date: Fri, 17 Jun 2022 08:48:31 +0200 [thread overview]
Message-ID: <5089ee52c1200a0525eb25e9ac2e1a6e00661f01.camel@suse.com> (raw)
In-Reply-To: <950f4ffe-7cf6-b385-1141-f27fbf5ebef9@gmail.com>
On Thu, 2022-06-16 at 22:32 +0200, Xose Vazquez Perez wrote:
> On 4/1/22 12:20, Martin Wilck wrote:
>
> > On Mon, 2022-03-28 at 19:57 +0200, Xose Vazquez Perez wrote:
> > > On 3/28/22 19:48, Martin Wilck wrote:
> > > > On Mon, 2022-03-28 at 19:04 +0200, Xose Vazquez Perez wrote:
> > > > > Cc: Martin Wilck <mwilck@suse.com>
> > > > > Cc: Benjamin Marzinski <bmarzins@redhat.com>
> > > > > Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
> > > > > Cc: DM-DEVEL ML <dm-devel@redhat.com>
> > > > > Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
> > > > > ---
> > > > > README.nvme | 12 ++++++++++++
> > > > > 1 file changed, 12 insertions(+)
> > > > > create mode 100644 README.nvme
> > > >
> > > > Why another separate README with just 12 lines?
> > > >
> > > > Martin
> > >
> > > README.md is intended multipath-tools developers.
> > > And README.alua and README.nvme are for sysadmins.
> > >
> >
> > I see no fundamental reason not to merge all READMEs into one,
> > and create "sysadmin" and "developer" sections.
>
> README.md is in markdown syntax.
> README.alua and README.nvme are plain text, and its content is easier
> to identify.
> Are you running out of inodes? :-)
No, it' about user friendliness. These .txt files are developer-level
documentation, while ALUA and NVMe are topic which are at least as
important to users as for developers. Distributions tend to ship the
READMEs under /usr/share/doc, but to be realistic, how many users still
look there for documentation these days?
Regards,
Martin
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2022-06-17 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 17:04 [dm-devel] [PATCH] multipath-tools: add basic info on how to use multipath-tools with NVMe devices Xose Vazquez Perez
2022-03-28 17:48 ` Martin Wilck
2022-03-28 17:57 ` Xose Vazquez Perez
2022-04-01 10:20 ` Martin Wilck
2022-06-16 20:32 ` Xose Vazquez Perez
2022-06-17 6:48 ` Martin Wilck [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=5089ee52c1200a0525eb25e9ac2e1a6e00661f01.camel@suse.com \
--to=mwilck@suse.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=xose.vazquez@gmail.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 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.