From: Bob Copeland <me@bobcopeland.com>
To: linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
viro@zeniv.linux.org.uk
Subject: Upstream tree for OMFS?
Date: Mon, 12 Jul 2010 11:49:01 -0400 [thread overview]
Message-ID: <AANLkTilI-GLcmJjC5n2aT-0ywdOK0M5VGSUdEGYXa3VJ@mail.gmail.com> (raw)
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.
--
Bob Copeland %% www.bobcopeland.com
next reply other threads:[~2010-07-12 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 15:49 Bob Copeland [this message]
2010-07-12 17:44 ` Upstream tree for OMFS? Andrew Morton
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=AANLkTilI-GLcmJjC5n2aT-0ywdOK0M5VGSUdEGYXa3VJ@mail.gmail.com \
--to=me@bobcopeland.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--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).