From: Theodore Tso <tytso@mit.edu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>, Mingming Cao <cmm@us.ibm.com>,
linux-ext4@vger.kernel.org
Subject: Re: Patch collision: 64-bit quota changes and ext4 delalloc quota changs
Date: Wed, 5 Nov 2008 12:40:26 -0500 [thread overview]
Message-ID: <20081105174026.GB29880@mit.edu> (raw)
In-Reply-To: <20081105084303.ed0c53d5.akpm@linux-foundation.org>
On Wed, Nov 05, 2008 at 08:43:03AM -0800, Andrew Morton wrote:
>
> It works for me. I really need to get off my butt and get -mm into
> linux-next.
>
> I can merge ext4-quota-handling-for-delayed-allocation.patch if you
> like, or you can merge it once te quota changes have gone in.
>
If you are willing to carry the
ext4-quota-handling-for-delayed-allocation.patch, that would be great.
Mingming, what I'll do is create a branch of the ext4 patch queue
(since it's being maintained in git anyway), that basically reflects
the patch queue as it currently exists today. You can do your
development in that branch so it won't impact you terribly, but I'll
then set master branch of the ext4 patch queue to be a version that
drops all of the quota related changes. You should be able to
periodically pull from the master branch to the quota branch, so you
can keep up with other changes, but then what we'll need to do is to
make sure that the version of the patches that you are developing
against in your branch corresponds with what Andrew has in mmotm, and
if it doesn't, we'll have to manually send updates to Andrew to keep
his tree in sync with yours, since it is his tree that will ultimately
be pushing the patches to Linus.
If it weren't for the fact that Jan is on vacation until November
18th, what I would have suggested instead was for Jan to create his
own quota git tree, drop the ext4 delalloc quota patches into a
separate git tree, called the quota-ext4-postmerge tree, and then tell
Steve to pull into next first the ext4 tree, then the quota tree, and
then the quota-ext4-postmerge tree. (And then we could easily do
testing/development by creating a throw-away integration tree that
merged the ext4, quota, and post-merge trees.)
But keeping this stuff all in -mm should work, although depending on
how many more cleanup patches flow into ext4, this might cause some
minor patch conflicts on that last quota dellaloc patch that actually
touches ext4 core code.
- Ted
next prev parent reply other threads:[~2008-11-05 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 16:09 Patch collision: 64-bit quota changes and ext4 delalloc quota changs Theodore Ts'o
2008-11-05 16:43 ` Andrew Morton
2008-11-05 17:40 ` Theodore Tso [this message]
2008-11-05 18:59 ` Mingming Cao
2008-11-05 19:16 ` Andrew Morton
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=20081105174026.GB29880@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=cmm@us.ibm.com \
--cc=jack@suse.cz \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).