From: Jeff Garzik <jeff@garzik.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
open-osd mailing-list <osd-dev@open-osd.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [GIT PULL] Request for pulling exofs for 2.6.30
Date: Thu, 02 Apr 2009 12:44:52 -0400 [thread overview]
Message-ID: <49D4EB84.6020100@garzik.org> (raw)
In-Reply-To: <49D4E70A.9090507@panasas.com>
Boaz Harrosh wrote:
> which is available in the git repository at:
>
> git://git.open-osd.org/linux-open-osd.git for-linus
>
> Boaz Harrosh (9):
> exofs: Kbuild, Headers and osd utils
> exofs: file and file_inode operations
> exofs: symlink_inode and fast_symlink_inode operations
> exofs: address_space_operations
> exofs: dir_inode and directory operations
> exofs: super_operations and file_system_type
> exofs: export_operations
> exofs: Documentation
> fs: Add exofs to Kernel build
For what little weight I have in this area... ACK
But I would suggest _not_ splitting up the add-filesystem patch. You
really only want to split up this stuff for review.
The add-exofs change is one single logical change, and splitting it up
across multiple changesets is not the most optimal nor bisect-safe approach.
Jeff
prev parent reply other threads:[~2009-04-02 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 16:25 [GIT PULL] Request for pulling exofs for 2.6.30 Boaz Harrosh
2009-04-02 16:44 ` Jeff Garzik [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=49D4EB84.6020100@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 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.