All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	"Theodore Ts'o" <tytso@mit.edu>, Mingming Cao <cmm@us.ibm.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Patch queue update
Date: Thu, 24 Jan 2008 10:32:17 -0600	[thread overview]
Message-ID: <4798BD91.20108@redhat.com> (raw)
In-Reply-To: <20080124162656.GJ18433@webber.adilger.int>

Andreas Dilger wrote:
> On Jan 24, 2008  20:20 +0530, Aneesh Kumar K.V wrote:
>> @@ -89,6 +89,8 @@ When mounting an ext4 filesystem, the following option are accepted:
>>  extents			ext4 will use extents to address file data.  The
>>  			file system will no longer be mountable by ext3.
>>  
>> +noextents		ext4 will not use extents for new files created.
>> +
> 
> s/new files created/newly created files/

Would a blurb about keeping ext3 disk-format compatibility be worthwhile
here?

>>  journal_checksum	Enable checksumming of the journal transactions.
>>  			This will allow the recovery code in e2fsck and the
>>  			kernel to detect corruption in the kernel.  It is a
>> @@ -206,6 +208,10 @@ nobh			(a) cache disk block mapping information
>>  			"nobh" option tries to avoid associating buffer
>>  			heads (supported only for "writeback" mode).
>>  
>> +mballoc		(*)	Use the mutliblock allocator for block allocation

speeeeling on "mutliblock" too :)

-Eric

  reply	other threads:[~2008-01-24 16:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 14:50 Patch queue update Aneesh Kumar K.V
2008-01-24 16:26 ` Andreas Dilger
2008-01-24 16:32   ` Eric Sandeen [this message]
2008-01-24 19:50 ` Mingming Cao
  -- strict thread matches above, loose matches on Subject: below --
2008-06-15 17:21 Aneesh Kumar K.V
2008-06-16 17:49 ` Aneesh Kumar K.V
2008-06-16 22:03   ` Mingming
2008-01-10 15:33 patch " Aneesh Kumar K.V
2008-01-10 21:43 ` Andreas Dilger
2008-01-11  4:09   ` Aneesh Kumar K.V
2007-12-24  6:30 Patch " Aneesh Kumar K.V

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=4798BD91.20108@redhat.com \
    --to=sandeen@redhat.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cmm@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.