public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Jeff Dike <jdike@addtoit.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] 2.6.8-rc4-mm1 - Fix UML build
Date: Wed, 18 Aug 2004 11:28:43 -0700	[thread overview]
Message-ID: <20040818182843.GA7749@taniwha.stupidest.org> (raw)
In-Reply-To: <20040817112629.04c7f672.akpm@osdl.org>

On Tue, Aug 17, 2004 at 11:26:29AM -0700, Andrew Morton wrote:

> Frankly, when a subsystem gets this far out of date I don't think it
> matters a lot - nobody has much hope of following all the changes
> anyway.  We'll just merge the megapatch on the assumption that Jeff
> knows what he's doing, and that it's better than what we had before.
> You should have seen the size of some of those MIPS patches ;)

I've been pushing for a large giant UML merge for ages, mostly as
nobody is looking over the broken down patches much anyhow...

I'd even be happy with the current stuff being shoved into mainline
even if it doesn't build for a few days until it gets fixed --- not
having a common point of reference is really quite frustrating.

There are a ton of white-space cleanups and sparsification changes
that could be done too --- I assume this would be best done *before* a
giant-patch merge?


  --cw

  parent reply	other threads:[~2004-08-18 18:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12  4:14 [PATCH 1/3] 2.6.8-rc4-mm1 - Fix UML build Jeff Dike
2004-08-15 22:06 ` Andrew Morton
2004-08-17  6:02   ` Jeff Dike
2004-08-17  5:06     ` William Lee Irwin III
2004-08-17  5:10       ` Andrew Morton
2004-08-17 14:45         ` Sam Ravnborg
2004-08-17 12:51           ` Russell King
2004-08-17  5:08     ` Andrew Morton
2004-08-17 19:15       ` Jeff Dike
2004-08-17 18:26         ` Andrew Morton
2004-08-18  2:58           ` Jeff Dike
2004-08-18 18:28           ` Chris Wedgwood [this message]
2004-08-17  8:55     ` Andreas Schwab
2004-08-17 18:17       ` Jeff Dike

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=20040818182843.GA7749@taniwha.stupidest.org \
    --to=cw@f00f.org \
    --cc=akpm@osdl.org \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@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