linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] FS_NOATIME for ocfs
Date: Wed, 14 Dec 2005 17:47:02 -0500	[thread overview]
Message-ID: <43A0A0E6.8030303@pobox.com> (raw)
In-Reply-To: <20051213175646.GD17130@lst.de>

Christoph Hellwig wrote:
> Although I think ocfs should still go into 2.6.15 a an additional driver
> that stands on it's own..

I ACK the inclusion of ocfs as well, but not in 2.6.15.

Standalone or not, we don't need to set an example of including new 
features at the last minute.  That just encourages other folks to submit 
new features at the last minute.  Which leads to lack of review, and 
unnecessary last minute work for some.  Do that enough times, and you'll 
be seeing reiser4 sent to Linus 24 hours before each -final release :)

	Jeff






      reply	other threads:[~2005-12-14 22:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13 17:56 [PATCH 4/6] FS_NOATIME for ocfs Christoph Hellwig
2005-12-14 22:47 ` Jeff Garzik [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=43A0A0E6.8030303@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@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).