[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120309223728.GD5635@thunk.org>
Date: Fri, 9 Mar 2012 17:37:28 -0500
From: Ted Ts'o <tytso@....edu>
To: "Darrick J. Wong" <djwong@...ibm.com>
Cc: Andreas Dilger <adilger.kernel@...ger.ca>,
Sunil Mushran <sunil.mushran@...cle.com>,
Amir Goldstein <amir73il@...il.com>,
Andi Kleen <andi@...stfloor.org>,
Mingming Cao <cmm@...ibm.com>,
Joel Becker <jlbec@...lplan.org>, linux-ext4@...r.kernel.org,
Coly Li <colyli@...il.com>
Subject: Re: [PATCH v3 00/54] e2fsprogs: Add metadata checksumming
I've imported this patch set into a guilt patch series, which makes it
easier for me to work on the patch series and make minor tweaks so
that I can get interim e2fsprogs support up and going (and at least
building and passing the regression test suite) so I can test and play
with the kernel side patches.
People who want to follow along can look here:
https://github.com/tytso/e2fsprogs-cksum-patch-queue
... or at the read-only git tree which you can find here:
git://github.com/tytso/e2fsprogs-cksum-patch-queue.git
With these large patch series it's easier for me to make blanket
changes to fix minor annoyances (such as commit descriptions which are
too wide and make "git log" displays hard to follow) or to merge
patches that are too fine grained[1] together.
Open source project management theory says that it's better to ask the
submitter to do all of this work, but given certain special
circumstances in this particular case, I decided to make the cleanup
work that I do publicly visible, as a compromise. I'll also make some
comments about some of the issues I find (and fix) by replying to the
emails on this mail thread.
This patch series will be maintained so that it can be applied to the
top-most "maint" branch of e2fsprogs.
Darrick, if you have time and would like to make further changes, ping
me off-line and I would be happy to give you write access to the
github tree.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists