From: Andreas Dilger <adilger@sun.com>
To: Felipe Franciosi <ozzy@doc.ic.ac.uk>
Cc: Theodore Tso <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: Simple inode question (ext2/3)
Date: Tue, 24 Feb 2009 21:06:54 -0700 [thread overview]
Message-ID: <20090225040654.GT3199@webber.adilger.int> (raw)
In-Reply-To: <alpine.DEB.2.00.0902242148450.13652@pintail.doc.ic.ac.uk>
On Feb 24, 2009 21:48 +0000, Felipe Franciosi wrote:
>> This isn't for some college class, is it?
>
> No, it is not. Where would you get that idea from?
Because there are lots of questions like this from university
students that would rather have the mailing list do their
homework for them.
> To be very honest with you, I don't see why you are wasting your time
> questioning me about these things instead of simply answering what I've
> asked or saying something like: "Have a look at brelse() and the inode
> bitmap manipulation routines used in ialloc.c".
>
> I'm beginning to believe you didn't know the answers to my questions,
> Ted. How sad.
How sad that you have just been rude one of the main ext2/3/4 developers,
e2fsprogs maintainer, and one of the most senior Linux kernel developers.
I would suggest that you look at what ext2_iget->ext2_get_inode() is doing.
You will have a hard time getting much help from the list unless you change
your attitude.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-02-25 4:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 17:13 Simple inode question (ext2/3) Felipe Franciosi
2009-02-24 18:12 ` Felipe Franciosi
2009-02-24 19:07 ` Theodore Tso
2009-02-24 19:32 ` Felipe Franciosi
2009-02-24 21:05 ` Theodore Tso
2009-02-24 21:48 ` Felipe Franciosi
2009-02-25 4:06 ` Andreas Dilger [this message]
2009-02-25 10:59 ` Felipe Franciosi
2009-02-25 13:11 ` Theodore Tso
2009-02-25 14:10 ` Greg Freemyer
2009-02-25 14:38 ` Theodore Tso
2009-03-28 7:57 ` SandeepKsinha
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=20090225040654.GT3199@webber.adilger.int \
--to=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ozzy@doc.ic.ac.uk \
--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 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).