Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] NLM: Revert parts of commit 24e36663
Date: Fri, 26 Sep 2008 18:22:05 -0400	[thread overview]
Message-ID: <1222467725.15581.5.camel@localhost> (raw)
In-Reply-To: <215DBAD9-1E4B-4E23-9F54-AAF6518D24DA@oracle.com>

On Fri, 2008-09-26 at 17:11 -0400, Chuck Lever wrote:
> If I know in advance when you (and Bruce) are taking new features or  
> bug fixes for each kernel release, that would be helpful.

That won't happen.

Send it when it is _ready_. That is the way everyone else works when
doing Linux kernel development...

If it needs to go into a particular kernel release, either because it is
a bugfix for a known problem, or because other patches depend upon it,
then make a special case for that.

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com

  reply	other threads:[~2008-09-26 22:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 18:50 [PATCH] NLM: Revert parts of commit 24e36663 Chuck Lever
     [not found] ` <20080924184732.4078.83334.stgit-lQeC5l55kZ7wdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-24 18:54   ` Trond Myklebust
2008-09-26 15:50     ` Talpey, Thomas
2008-09-25 21:38   ` J. Bruce Fields
2008-09-26 17:53     ` Chuck Lever
2008-09-26 18:45       ` J. Bruce Fields
2008-09-26 18:49         ` Trond Myklebust
2008-09-26 18:51           ` J. Bruce Fields
2008-09-26 19:04           ` Chuck Lever
2008-09-26 19:11             ` Trond Myklebust
2008-09-26 19:44               ` J. Bruce Fields
2008-09-26 19:54                 ` Chuck Lever
2008-09-26 19:57                   ` Trond Myklebust
2008-09-26 21:11                     ` Chuck Lever
2008-09-26 22:22                       ` Trond Myklebust [this message]
2008-09-26 23:30                       ` J. Bruce Fields

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=1222467725.15581.5.camel@localhost \
    --to=trond.myklebust@netapp.com \
    --cc=bfields@fieldses.org \
    --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