From: Evgeniy Polyakov <zbr@ioremap.net>
To: Joe Perches <joe@perches.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-fsdevel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [take 3] pohmelfs: call for inclusion
Date: Thu, 22 Mar 2012 00:27:02 +0400 [thread overview]
Message-ID: <20120321202702.GA16713@ioremap.net> (raw)
In-Reply-To: <1331907127.5406.48.camel@joe2Laptop>
Hi
On Fri, Mar 16, 2012 at 07:12:07AM -0700, Joe Perches (joe@perches.com) wrote:
> If you haven't already, you could setup a public git tree
> somewhere to make it easier to track changes and make a
> request for inclusion in linux-next.
>
> I think you just need to send a request to:
> Stephen Rothwell <sfr@canb.auug.org.au>
I'm cooking up a tree hosted on ioremap.net for tomorrow, which will be
rebased against current tree. It will incorporate your -next pohmelfs patches.
If hosting it at ioremap.net is not suitable, then Stephen, I send a
request :)
Then I will send next pull request to Linus "always-keeping-silence" Torvalds
--
Evgeniy Polyakov
next prev parent reply other threads:[~2012-03-21 20:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 12:18 [take 3] pohmelfs: call for inclusion Evgeniy Polyakov
2012-03-16 13:29 ` Joe Perches
2012-03-16 13:39 ` Evgeniy Polyakov
2012-03-16 13:43 ` Evgeniy Polyakov
2012-03-16 14:12 ` Joe Perches
2012-03-21 20:27 ` Evgeniy Polyakov [this message]
2012-03-21 21:02 ` Linus Torvalds
2012-03-21 21:18 ` Al Viro
2012-03-21 21:37 ` Evgeniy Polyakov
2012-03-21 21:54 ` Al Viro
2012-03-21 22:04 ` Evgeniy Polyakov
2012-03-21 22:28 ` Al Viro
2012-03-21 22:40 ` Evgeniy Polyakov
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=20120321202702.GA16713@ioremap.net \
--to=zbr@ioremap.net \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=joe@perches.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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).