From: Christoph Hellwig <hch@infradead.org>
To: Wendy Cheng <wcheng@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [Fwd: [PATCH 0/4 Revised] NLM - lock failover]
Date: Wed, 18 Apr 2007 16:35:04 +0100 [thread overview]
Message-ID: <20070418153504.GA3805@infradead.org> (raw)
In-Reply-To: <46257E41.4060606@redhat.com>
On Tue, Apr 17, 2007 at 10:11:13PM -0400, Wendy Cheng wrote:
> However, since this particular NLM patch set is only part of the overall
> scaffolding code to allow NFS V3 server fail over before NFS V4 is
> widely adopted and stabilized, I'm wondering whether we should drag
> ourselves too far for something that will be replaced soon.
I don't think that's a valid argument. We hack this up because it's
going to be obsolete mid-term never was a really good argument. And in
this case it's a particularly bad one. People won't rush to NFSv4 just
because someone declares it stable now. And if they did we couldn't
simply rip out existing functionality.
So please do it properly.
More comments on the rest of the mail later when I have a little more
time at my hand.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-04-18 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 2:11 [Fwd: [PATCH 0/4 Revised] NLM - lock failover] Wendy Cheng
2007-04-18 15:35 ` Christoph Hellwig [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=20070418153504.GA3805@infradead.org \
--to=hch@infradead.org \
--cc=nfs@lists.sourceforge.net \
--cc=wcheng@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 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.