From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 03/15] ocfs2: Move directory manipulation code into dir.c
Date: Thu Sep 20 11:30:21 2007 [thread overview]
Message-ID: <20070920182944.GF30391@tasint.org> (raw)
In-Reply-To: <200709192012.l8JKCGjS012156@agmgw2.us.oracle.com>
On Fri, Sep 07, 2007 at 06:21:26PM -0700, Mark Fasheh wrote:
> The code for adding, removing, deleting directory entries was splattered all
> over namei.c. I'd rather have this all centralized, so that it's easier to
> make changes for inline dir data, and eventually indexed directories.
>
> None of the code in any of the functions was changed. I only removed the
> static keyword from some prototypes so that they could be exported.
>
> Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
Signed-off-by: Joel Becker <joel.becker@oracle.com>
--
Life's Little Instruction Book #444
"Never underestimate the power of a kind word or deed."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
prev parent reply other threads:[~2007-09-20 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 13:12 [Ocfs2-devel] [PATCH 03/15] ocfs2: Move directory manipulation code into dir.c Mark Fasheh
2007-09-20 11:30 ` Joel Becker [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=20070920182944.GF30391@tasint.org \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 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.