From: Andrew Morton <akpm@osdl.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-ext4@vger.kernel.org, cmm@us.ibm.com, shaggy@austin.ibm.com
Subject: Re: + ext4-enable.patch added to -mm tree
Date: Thu, 5 Oct 2006 22:07:48 -0700 [thread overview]
Message-ID: <20061005220748.2d124f57.akpm@osdl.org> (raw)
In-Reply-To: <20061005215941.f0681c66.rdunlap@xenotime.net>
On Thu, 5 Oct 2006 21:59:41 -0700
Randy Dunlap <rdunlap@xenotime.net> wrote:
> > +config EXT4DEV_FS
> > + tristate "Ext4dev/ext4 extended fs support development (EXPERIMENTAL)"
> > + depends on EXPERIMENTAL
> > + select JBD
> > + help
>
> ugh, I'm getting seasick from looking at that indentation.
> I don't have an ext4 patchset ATM, but I'll fix that if no one
> else does.
That's someone's broken tab key again. I fixed up my copy of that patch.
prev parent reply other threads:[~2006-10-06 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200610060036.k960aB76011550@shell0.pdx.osdl.net>
2006-10-06 4:59 ` + ext4-enable.patch added to -mm tree Randy Dunlap
2006-10-06 5:07 ` Andrew Morton [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=20061005220748.2d124f57.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=shaggy@austin.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox