From: matthieu castet <castet.matthieu@free.fr>
To: Linux Kernel list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>,
joern@logfs.org, linux-mtd@lists.infradead.org
Subject: Re: LogFS merge
Date: Sat, 03 May 2008 11:29:43 +0200 [thread overview]
Message-ID: <481C3087.8020501@free.fr> (raw)
Hi,
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?
Shouldn't this get review by mtd guys first ?
Also for info, there have been some issue raised by the ubifs developer [1].
Matthieu
[1] http://thread.gmane.org/gmane.linux.kernel/658740/focus=660392
next reply other threads:[~2008-05-03 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 9:29 matthieu castet [this message]
2008-05-03 12:00 ` LogFS merge Jörn Engel
2008-05-04 16:20 ` Thomas Gleixner
2008-05-04 18:04 ` Josh Boyer
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=481C3087.8020501@free.fr \
--to=castet.matthieu@free.fr \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=torvalds@osdl.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