From: NeilBrown <neilb@suse.de>
To: Sebastien Godard <sysstat@orange.fr>
Cc: Steve Dickson <SteveD@redhat.com>,
Chuck Lever <chuck.lever@oracle.com>,
varekova@redhat.com,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Too many programs called nfsiostat.
Date: Sun, 26 Jan 2014 07:45:57 +1100 [thread overview]
Message-ID: <20140126074557.6baf15c8@notabene.brown> (raw)
In-Reply-To: <52E3DC2C.1050400@orange.fr>
[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]
On Sat, 25 Jan 2014 16:45:48 +0100 Sebastien Godard <sysstat@orange.fr> wrote:
> On 01/25/2014 03:39 PM, Steve Dickson wrote:
> >
> > On 23/01/14 15:12, Sebastien Godard wrote:
> >> On 01/23/2014 06:42 PM, Steve Dickson wrote:
> >>> On 22/01/14 16:52, NeilBrown wrote:
> >>>> On Wed, 22 Jan 2014 08:12:35 -0500 Steve Dickson <SteveD@redhat.com> wrote:
> >>>>
> >>>>> On 21/01/14 19:24, NeilBrown wrote:
> >>>>> Is this version still actively being maintain?
> >>>> Last change was 5 days ago.
> >>>>
> >>>> https://github.com/sysstat/sysstat/commits/master/nfsiostat.c
> >>> I guess the question now is do they want to continue maintaining
> >>> it or just merge the functionality into the nfs-utils version...
> >>>
> >> This is no longer a question as I already answered it. Please *read* my previous mail.
> > I did... but thought Neil's mail was pointing out that some type of
> > maintenance was happening... But if you say it's "no longer actively being maintained"
> > I'll believe you... :-)
> >
> > So what is the next step to deprecate the nfsiostat in sysstat?
> >
>
> In fact, the various patches applied to nfsiostat over the last few
> years were mainly cosmetic ones (changes in sysstat APIs, etc.)
> So I propose now to simply remove nfsiostat code from sysstat: Next
> sysstat version will rename nfsiostat (eg. to nfsiostat-sysstat) and the
> man page will indicate it is now obsolete and point to the version from
> nfs-utils. Then nfsiostat will be definitively removed sometime before
> the end of this year.
>
> Regards,
>
Fantastic - a nice clear resolution, just what I was hoping for.
Thanks a lot!
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2014-01-25 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 23:46 Too man programs calls nfsiostat NeilBrown
2014-01-21 3:00 ` Too many " NeilBrown
2014-01-21 3:45 ` NeilBrown
2014-01-21 15:40 ` Chuck Lever
2014-01-22 0:24 ` Too many programs called nfsiostat NeilBrown
2014-01-22 13:12 ` Steve Dickson
2014-01-22 21:41 ` Sebastien Godard
2014-01-22 21:52 ` NeilBrown
2014-01-23 17:42 ` Steve Dickson
2014-01-23 20:12 ` Sebastien Godard
2014-01-25 14:39 ` Steve Dickson
2014-01-25 15:45 ` Sebastien Godard
2014-01-25 20:45 ` NeilBrown [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=20140126074557.6baf15c8@notabene.brown \
--to=neilb@suse.de \
--cc=SteveD@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sysstat@orange.fr \
--cc=varekova@redhat.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