From: Joel Becker <jlbec@evilplan.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Mark Fasheh <mfasheh@suse.de>,
Richard Weinberger <richard@nod.at>,
ocfs2-devel@oss.oracle.com, ocfs2-user@oss.oracle.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
david@sigma-star.at
Subject: Re: OCFS2 mainline state?
Date: Sat, 2 Mar 2013 02:05:41 -0800 [thread overview]
Message-ID: <20130302100540.GB22177@localhost> (raw)
In-Reply-To: <20130225211617.GF4503@ZenIV.linux.org.uk>
On Mon, Feb 25, 2013 at 09:16:18PM +0000, Al Viro wrote:
> On Mon, Feb 25, 2013 at 01:11:03PM -0800, Mark Fasheh wrote:
>
> > I've seen that patch actually and yes it should have been in mainline
> > already. I didn't see whether it's in -mm (Andrew is pickup up some of the
> > patches for us right now).
> >
> > I'll check and if it's not I'll try to send him a version of it today.
>
> Normally filesystem trees are fed to Linus... Or I can pick that patch via
> VFS tree (and send it to Linus tomorrow). There also had been Jan's ocfs2
> patch a while ago; I picked only the VFS part of that series, ext* and
> IIRC xfs ones went to corresponding filesystem trees. Should I just pick
> the ocfs2 stuff from now on?
Andrew's been picking it up. I'm doing the Acked-by thing, until I have
a test environment back. Thank you for offering, and if Andrew gets
tired of it before I'm fully operational, we'll happily take you up on
this.
Joel
--
"There is no more evil thing on earth than race prejudice, none at
all. I write deliberately -- it is the worst single thing in life
now. It justifies and holds together more baseness, cruelty and
abomination than any other sort of error in the world."
- H. G. Wells
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2013-03-02 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 20:33 OCFS2 mainline state? Richard Weinberger
2013-02-25 21:11 ` Mark Fasheh
2013-02-25 21:16 ` Al Viro
2013-02-25 21:28 ` Mark Fasheh
2013-03-02 10:05 ` Joel Becker [this message]
2013-02-25 21:30 ` Mark Fasheh
2013-02-25 21:37 ` Smart Weblications GmbH - Florian Wiessner
2013-03-02 10:15 ` Vincent ETIENNE
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=20130302100540.GB22177@localhost \
--to=jlbec@evilplan.org \
--cc=david@sigma-star.at \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.de \
--cc=ocfs2-devel@oss.oracle.com \
--cc=ocfs2-user@oss.oracle.com \
--cc=richard@nod.at \
--cc=viro@ZenIV.linux.org.uk \
/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).