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

On Fri, Sep 26, 2008 at 05:11:25PM -0400, Chuck Lever wrote:
> On Sep 26, 2008, at Sep 26, 2008, 3:57 PM, Trond Myklebust wrote:
>> On Fri, 2008-09-26 at 15:54 -0400, Chuck Lever wrote:
>>> The whole system makes it absolutely impossible to plan features and
>>> bug fixes.
>>
>> The only thing it makes impossible is planning features for a
>> _particular_ kernel revision.
>
> I find it impossible to plan for a particular _year_ (or even two).
>
> The problem is _you_, the subsystem maintainer, have a merge window too.  
> I find it challenging to align my patch submissions with two sliding 
> merge windows that open and close at arbitrary times without any warning 
> whatever.  And now I have to worry about Bruce's merge window as well....

Please just send them in whenever they're ready--I mean to take patches
at any time, and then decide separately whether they should be queued up
for the current version, the next one, and/or the previous (stable)
version.  There are inevitably delays (especially with vacations and
such), but normally I'll try to at least respond with an estimate if
it's going to take longer than a couple days.

> Plus, the submission guidelines keep changing.  FreeBSD has an amazing  
> guide to kernel development rules and conventions posted on the web.  I 
> wish Linux had the same.

Do you have a pointer to it, and/or suggestions how it could be used to
improve existing linux documentation?

There's Documentation/SubmittingPatches and stuff.  My main gripe with
Documentation/ is that people contribute to it, but there's no
maintainer to say "no" or to keep things organized, so it tends to get
large and messy over time.

In any case lkml would be a better forum for this.

> If I know in advance when you (and Bruce) are taking new features or bug 
> fixes for each kernel release, that would be helpful.

I'd like to say the answer is "any time", barring occasional
interruptions.

Or if the problem is that you've got stuff that you're basically done
with, but that you know you *might* get the chance to take one more look
at if you had another week--I think it'd be better if people just sent
stuff in when they think it's good enough, and if we later find a
problem we'll fix it.

--b.

      parent reply	other threads:[~2008-09-26 23:31 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
2008-09-26 23:30                       ` J. Bruce Fields [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=20080926233056.GM7138@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.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