From: Andrew Morton <akpm@linux-foundation.org>
To: Bob Copeland <me@bobcopeland.com>
Cc: linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
linux-next@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Upstream tree for OMFS?
Date: Mon, 12 Jul 2010 10:44:35 -0700 [thread overview]
Message-ID: <20100712104435.2ca47c0a.akpm@linux-foundation.org> (raw)
In-Reply-To: <AANLkTilI-GLcmJjC5n2aT-0ywdOK0M5VGSUdEGYXa3VJ@mail.gmail.com>
On Mon, 12 Jul 2010 11:49:01 -0400 Bob Copeland <me@bobcopeland.com> wrote:
> Hello fs devs,
>
> I have a few patches to send on to -next for OMFS
> and I finally got around to setting up a git tree for
> it. Previously I sent things through akpm or the
> trivial tree.
>
> I doubt anyone but me cares too much about this FS
> but I thought I'd ask first if anyone wants to be the
> upstream instead of me sending pull requests directly
> to Linus. Of course I'll post patches here for
> review in either case.
Please ask Stephen to include the tree in the linux-next lineup.
next prev parent reply other threads:[~2010-07-12 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 15:49 Upstream tree for OMFS? Bob Copeland
2010-07-12 17:44 ` Andrew Morton [this message]
2010-07-12 22:13 ` Bob Copeland
2010-07-13 13:03 ` Stephen Rothwell
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=20100712104435.2ca47c0a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=sfr@canb.auug.org.au \
--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).