From: Pavel Machek <pavel@suse.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: Mingming Cao <cmm@us.ibm.com>, Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/5] Forking ext4 filesystem and JBD2
Date: Mon, 14 Aug 2006 21:44:43 +0000 [thread overview]
Message-ID: <20060814214442.GB4032@ucw.cz> (raw)
In-Reply-To: <20060810100012.abc1b5a1.akpm@osdl.org>
Hi!
> > We do maintain a quilt(akpm) style patches on http://ext2.sf.net, the
> > latest patches are always at
> > http://ext2.sourceforge.net/48bitext3/patches/latest/
> >
> > We thought about doing git initially, still open for that doing do, if
> > it's more preferable by Linus or Andrew. Just thought it's a lot
> > easiler for non git user to pull the patches from a project website.
> >
>
> We should aim to get the big copy-ext3-to-ext4 patch into Linus's tree as
> early as possible.
>
> I'm just not sure when to do that. Immediately after 2.6.19-rc1 is
> released would be good because it is when every tree (including -mm) is in
> its most-synced-up state.
Or you could simply do it _now_. Its new-driver-like, so freeze should
not apply :-).
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-08-15 18:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 1:16 Mingming Cao
2006-08-10 5:58 ` Jeff Garzik
2006-08-10 16:33 ` Mingming Cao
2006-08-10 17:00 ` Andrew Morton
2006-08-14 21:44 ` Pavel Machek [this message]
2006-08-15 19:06 ` Jeff Garzik
2006-08-10 14:02 ` Michal Piotrowski
2006-08-10 15:15 ` Michal Piotrowski
[not found] ` <1155236801.3162.1.camel@localhost.localdomain>
2006-08-10 19:06 ` John McCutchan
[not found] ` <1156012970.9346.1.camel@localhost.localdomain>
2006-08-19 18:42 ` John McCutchan
2006-08-19 21:17 ` Michal Piotrowski
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=20060814214442.GB4032@ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®