From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: coly li <colyli@gmail.com>
Cc: "Jose R. Santos" <jrs@us.ibm.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: block groups with no inode tables
Date: Tue, 10 Jul 2007 12:40:32 -0500 [thread overview]
Message-ID: <1184089232.13379.6.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <1184088605.17636.1.camel@colyt43.site>
On Wed, 2007-07-11 at 01:30 +0800, coly li wrote:
> Hi, once we decide to do this, how about storing inode inside the
> directory ?
Which directory?
> IMHO, the latter one is more attractive :-)
Sounds like a mess to me. Consider ln and mv.
> Coly
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2007-07-10 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 17:12 block groups with no inode tables Jose R. Santos
2007-07-10 17:30 ` coly li
2007-07-10 17:40 ` Dave Kleikamp [this message]
2007-07-10 15:59 ` Mingming Cao
2007-07-10 19:09 ` Dave Kleikamp
2007-07-11 4:50 ` Andreas Dilger
2007-07-10 20:30 ` Theodore Tso
2007-07-11 4:31 ` Andreas Dilger
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=1184089232.13379.6.camel@kleikamp.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=colyli@gmail.com \
--cc=jrs@us.ibm.com \
--cc=linux-ext4@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).