From: Thiago Becker <tbecker@redhat.com>
To: Steve Dickson <steved@redhat.com>
Cc: linux-nfs@vger.kernel.org, trond.myklebust@hammerspace.com,
anna.schumaker@netapp.com, Olga Kornievskaia <kolga@netapp.com>
Subject: Re: [RFC v2 PATCH 0/7] Introduce nfs-readahead-udev
Date: Fri, 18 Mar 2022 12:13:47 -0300 [thread overview]
Message-ID: <CAD_rW4XEooKeN2ttG-tjxGfwybjRRhs_QsLAwSoqDFDbp7GAKA@mail.gmail.com> (raw)
In-Reply-To: <f6a1e306-211a-25d0-50c5-63c631ca1e47@redhat.com>
On Tue, Mar 15, 2022 at 8:54 AM Steve Dickson <steved@redhat.com> wrote:
> My apologies for waiting late on this... I was on PTO.
>
> I really don't like the name of the is command. It
> does not follow any of the naming conventions we used in the
> past... Can you please rename the command to nfsrahead.
I have this on my git, I'm just waiting for more comments to release a
new version.
> tia,
>
> steved.
thiago
prev parent reply other threads:[~2022-03-18 15:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 19:06 [RFC v2 PATCH 0/7] Introduce nfs-readahead-udev Thiago Becker
2022-03-11 19:06 ` [RFC v2 PATCH 1/7] Create nfs-readahead-udev Thiago Becker
2022-03-11 19:06 ` [RFC v2 PATCH 2/7] readahead: configure udev Thiago Becker
2022-03-11 19:06 ` [RFC v2 PATCH 3/7] readahead: create logging facility Thiago Becker
2022-03-11 19:06 ` [RFC v2 PATCH 4/7] readahead: only set readahead for nfs devices Thiago Becker
2022-03-11 19:06 ` [RFC v2 PATCH 5/7] readahead: create the configuration file Thiago Becker
2022-03-11 19:06 ` [RFC v2 PATCH 6/7] readahead: add mountpoint and fstype options Thiago Becker
2022-03-11 19:06 ` [RFC v2 PATCH 7/7] readahead: documentation Thiago Becker
2022-03-17 15:37 ` Steve Dickson
2022-03-18 15:11 ` Thiago Becker
2022-03-15 11:54 ` [RFC v2 PATCH 0/7] Introduce nfs-readahead-udev Steve Dickson
2022-03-18 15:13 ` Thiago Becker [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=CAD_rW4XEooKeN2ttG-tjxGfwybjRRhs_QsLAwSoqDFDbp7GAKA@mail.gmail.com \
--to=tbecker@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
--cc=trond.myklebust@hammerspace.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.