From: Andrew Morton <akpm@osdl.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: davidm@hpl.hp.com, jbarnes@sgi.com, pfg@sgi.com,
linux-kernel@vger.kernel.org, davidm@napali.hpl.hp.com
Subject: Re: [PATCH] Altix I/O code cleanup
Date: Mon, 13 Oct 2003 03:55:12 -0700 [thread overview]
Message-ID: <20031013035512.3859067d.akpm@osdl.org> (raw)
In-Reply-To: <20031013095824.B25495@infradead.org>
Christoph Hellwig <hch@infradead.org> wrote:
>
> On Fri, Oct 10, 2003 at 03:50:45PM -0700, David Mosberger wrote:
> > >>>>> On Fri, 10 Oct 2003 14:51:53 -0700, jbarnes@sgi.com (Jesse Barnes) said:
> >
> > Jesse> David, please apply this set of patches from Pat.
> >
> > Unfortunately, the 2.6 tree is closed for cleanups. I would _like_ to
> > see the patch applied, though. Perhaps you could talk to Andrew and
> > see if you can get an exception?
>
> Sounds strange to apply this rule for a particular årchitectured that
> just managed to compile again on 2.6 and has a huge backlog of cleanups
> and restructuring now...
Well there are two reasons for discouraging cleanups. The first is of
course that they can destabilise things. But the other is that we want as
many developers as possible (Hi, Jesse) concentrating on stabilisation.
I hereby introduce the "bugzilla tax". The cost of each cleanup is two
fixes for open bugzilla entries.
But if David really wants this change, and ongoing stabilisation work will
be based on top of it then yes, it probably should go in after good
testing.
next prev parent reply other threads:[~2003-10-13 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 21:49 Patrick Gefre
2003-10-10 21:51 ` Jesse Barnes
2003-10-10 22:50 ` David Mosberger
2003-10-10 23:51 ` Jesse Barnes
2003-10-13 8:58 ` Christoph Hellwig
2003-10-13 10:55 ` Andrew Morton [this message]
2003-10-13 14:06 ` Christoph Hellwig
2003-10-13 8:56 ` Christoph Hellwig
2003-10-15 8:07 ` Jes Sorensen
2003-10-15 12:55 ` Christoph Hellwig
2003-10-16 13:08 ` Jes Sorensen
2003-10-16 16:40 ` Colin Ngam
2003-10-17 8:11 ` Christoph Hellwig
2003-10-17 13:36 ` Jes Sorensen
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=20031013035512.3859067d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=hch@infradead.org \
--cc=jbarnes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pfg@sgi.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
all inboxes | Powered by JetHome®