From: Jan Kara <jack@suse.cz>
To: Theodore Tso <tytso@mit.edu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Tweedie <sct@redhat.com>,
linux-ext4@vger.kernel.org, Andreas Dilger <adilger@sun.com>
Subject: Re: A tree to pull into linux-next
Date: Thu, 16 Jul 2009 13:52:21 +0200 [thread overview]
Message-ID: <20090716115221.GA24875@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20090716114751.GE21267@mit.edu>
> On Thu, Jul 16, 2009 at 04:48:26PM +1000, Stephen Rothwell wrote:
> >
> > I am happy to include this, but (no offense) I would like to hear from
> > the ext3 and jbd maintainers (cc'd) about it.
> >
>
> The main isssue would be that akpm often has ext3 changes stashed in
> -mm. Having a separate ext3 tree makes sense, and if Jan wants to
> maintain it, that makes good sense to me, but we should get Andrew's
> sign off, and Jan should make sure he has any ext3/jbd patches that
> might be in -mm, to avoid any potential patch conflicts.
Yeah. It's upto Andrew. I think he pulls linux-next so he should notice
conflicts. Anyway, I don't mind pushing the changes through him if he
likes it more that way but I've felt that he's rather busy and this
hopefully helps him a bit...
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
next prev parent reply other threads:[~2009-07-16 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090715193742.GA18583@duck.suse.cz>
2009-07-16 6:48 ` A tree to pull into linux-next Stephen Rothwell
2009-07-16 10:45 ` Jan Kara
2009-07-16 11:56 ` Stephen C. Tweedie
2009-07-16 11:47 ` Theodore Tso
2009-07-16 11:52 ` Jan Kara [this message]
2009-07-21 6:08 ` Stephen Rothwell
2009-07-21 6:15 ` Andrew Morton
2009-07-21 6:27 ` 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=20090716115221.GA24875@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sct@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
/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