From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Jörn Engel" <joern@logfs.org>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linus Torvalds" <torvalds@osdl.org>,
"David Woodhouse" <dwmw2@infradead.org>,
"Arnd Bergmann" <arnd@arndb.de>,
linux-kernel@vger.kernel.org, "Christoph Hellwig" <hch@lst.de>,
"Al Viro" <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: Re: LogFS merge
Date: Fri, 2 May 2008 17:49:38 +0300 [thread overview]
Message-ID: <84144f020805020749r55d5bd3eta82b5cdadb5fffea@mail.gmail.com> (raw)
In-Reply-To: <20080502133234.GA24080@logfs.org>
Hi Jörn,
On Fri, May 2, 2008 at 4:32 PM, Jörn Engel <joern@logfs.org> wrote:
> not being familiar with either maintaining my own git tree or the -next
> process, I'd still like to get logfs into mainline. It has gone through
> six rounds of reviews and the last has been mostly about crossing some
> i's here and dotting some t's there.
>
> So should it simmer in -next and -mm for another month? Should it go
> straight into -linus?
You probably want an ACK from the VFS maintainers before aiming at
mainline. But it surely makes sense to ask Andrew to pull it in -mm
now.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2008-05-02 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080502133234.GA24080@logfs.org>
2008-05-02 14:49 ` Pekka Enberg [this message]
2008-05-02 15:31 ` LogFS merge Christoph Hellwig
2008-05-02 20:33 ` Jörn Engel
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=84144f020805020749r55d5bd3eta82b5cdadb5fffea@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@osdl.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).