From: Richard Purdie <rpurdie@openedhand.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nitin Gupta <nitingupta910@gmail.com>,
Adrian Bunk <bunk@stusta.de>,
Daniel Hazelton <dhazelton@enter.net>,
LKML <linux-kernel@vger.kernel.org>,
Hugh Dickins <hugh@veritas.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH -mm 0/5] LZO and swap write failure patches for -mm
Date: Tue, 05 Jun 2007 09:56:42 +0100 [thread overview]
Message-ID: <1181033802.6180.11.camel@localhost.localdomain> (raw)
In-Reply-To: <20070604225038.9973226b.akpm@linux-foundation.org>
On Mon, 2007-06-04 at 22:50 -0700, Andrew Morton wrote:
> I'd say go with the cleanups. The code I've seen is going to be quite
> unmaintainable by any kernel developer.
>
> Any fixes which come from upstream can be trivially applied by taking the
> diffs against the version of upstream we started with and manually applying
> them to our version. If the diffs are too large and complex for that then
> a) we shouldn't be merging the code in its current state anyway and b) with
> the code as-is we couldn't effectively review or changelog those diffs, so
> we shouldn't apply them.
>
> So just fork it and freeze it.
Ok, thanks for the decision.
Since I don't have too much faith in what Nitin has done with it, I'll
produce a version myself. In theory we should end up with identical code
so will be a sanity check of Nitin's code if nothing else.
Cheers,
Richard
next prev parent reply other threads:[~2007-06-05 8:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 15:36 [PATCH -mm 0/5] LZO and swap write failure patches for -mm Richard Purdie
2007-06-04 16:14 ` Daniel Hazelton
2007-06-04 16:52 ` Richard Purdie
2007-06-04 17:37 ` Daniel Hazelton
2007-06-04 18:34 ` Nitin Gupta
2007-06-04 20:45 ` Richard Purdie
2007-06-04 22:13 ` Daniel Hazelton
2007-06-04 18:26 ` Nitin Gupta
2007-06-04 20:06 ` Adrian Bunk
2007-06-05 5:30 ` Nitin Gupta
2007-06-05 5:50 ` Andrew Morton
2007-06-05 8:56 ` Richard Purdie [this message]
2007-06-04 20:58 ` Richard Purdie
2007-06-05 6:15 ` Christoph Hellwig
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=1181033802.6180.11.camel@localhost.localdomain \
--to=rpurdie@openedhand.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=dhazelton@enter.net \
--cc=dwmw2@infradead.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=nitingupta910@gmail.com \
/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