From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: phillips-sjnr1BIWhQJeoWH0uzbU5w@public.gmane.org
Cc: admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org,
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: Ready for production ?
Date: Sat, 18 Oct 2008 11:28:09 +0900 (JST) [thread overview]
Message-ID: <20081018.112809.61376981.ryusuke@osrg.net> (raw)
In-Reply-To: <200810170415.30644.phillips-sjnr1BIWhQJeoWH0uzbU5w@public.gmane.org>
Hi,
On Fri, 17 Oct 2008 04:15:30 -0700, Daniel Phillips wrote:
> I don't think you should hold back from merging with mainline just
> because of stability problems. If you are mostly working except for
> some small, hard to find problems, then get it merged, tell everybody
> about the problems, and let people go hunt for them. That is what
> the open source process is about.
> From what I can see, you are ready to go start the merging process
> now.
Thanks for the comment.
I have already submitted kernel patches of the nilfs2 to LKML, and now
the nilfs2 is in the Andrew's -mm patch set. Yes, I would like to
proceed merging with mainline, and I'm really working on that in
parallel. Your point is what I want to do.
The current focus is whether the nilfs2 is accepted by the kernel
community or not. I'd like to accelerate activity for the merging,
however I cannot work full-time for this. I would be thankful if
someone could help me for it. ;)
With regards,
Ryusuke Konishi
prev parent reply other threads:[~2008-10-18 2:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 20:44 Ready for production ? David Arendt
[not found] ` <48F65636.5050405-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
2008-10-17 6:09 ` Ryusuke Konishi
[not found] ` <20081017.150912.86504903.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-10-17 11:15 ` Daniel Phillips
[not found] ` <200810170415.30644.phillips-sjnr1BIWhQJeoWH0uzbU5w@public.gmane.org>
2008-10-18 2:28 ` Ryusuke Konishi [this message]
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=20081018.112809.61376981.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org \
--cc=phillips-sjnr1BIWhQJeoWH0uzbU5w@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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