From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Lans Carstensen <Lans.Carstensen@dreamworks.com>,
NFS list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 2/4] nfs-utils: nfs-iostat.py autofs cleanup and option to sort by ops/s
Date: Wed, 26 Aug 2009 11:13:03 -0400 [thread overview]
Message-ID: <4A9550FF.6010103@RedHat.com> (raw)
In-Reply-To: <3644941A-3EA7-4755-867A-888E81A372FC@oracle.com>
On 08/26/2009 10:28 AM, Chuck Lever wrote:
>
> On Aug 26, 2009, at 12:59 AM, Lans Carstensen wrote:
>
>> commit d3bb692a8c26c2d4e0dc70d7d0359daf79090e1e
>> Author: Lans Carstensen <Lans.Carstensen@dreamworks.com>
>> Date: Tue Aug 25 21:52:03 2009 -0700
>>
>> Bump nfs-iostat.py version up to 0.3 to reflect new features.
>
> Now that nfs-iostat.py has been integrated into nfs-utils, I'm not sure
> we want to maintain an individual version number for it. Maybe it
> should use the nfs-utils package's versioning instead... Steve, your
> thoughts?
Hmm... I don't think we tie any of other commands versions to
the package version.... Although it might be a good idea to do so,
but for this instance, since these commands are still incognito (there
are not man pages, which is on my plate), I think just bumping the
version is fine..
steved.
next prev parent reply other threads:[~2009-08-26 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 4:59 [PATCH 2/4] nfs-utils: nfs-iostat.py autofs cleanup and option to sort by ops/s Lans Carstensen
2009-08-26 14:28 ` Chuck Lever
2009-08-26 15:13 ` Steve Dickson [this message]
2009-08-26 15:35 ` Chuck Lever
2009-08-26 18:03 ` Steve Dickson
2009-08-26 20:28 ` Chuck Lever
2009-08-26 23:56 ` Lans Carstensen
2009-08-27 14:04 ` Chuck Lever
2009-08-27 14:17 ` Steve Dickson
-- strict thread matches above, loose matches on Subject: below --
2009-09-15 4:57 Lans Carstensen
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=4A9550FF.6010103@RedHat.com \
--to=steved@redhat.com \
--cc=Lans.Carstensen@dreamworks.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).