mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: davidm@hpl.hp.com, davidm@napali.hpl.hp.com,
	linux-ia64@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: milstone reached: ia64 linux builds out of Linus' tree
Date: 04 Aug 2003 20:07:58 +0100	[thread overview]
Message-ID: <1060024077.719.26.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030804114546.10786f84.davem@redhat.com>

On Llu, 2003-08-04 at 19:45, David S. Miller wrote:
> My point was that if some random single monkey like me can keep a
> loser platform like sparc64 still building in Linus's tree, a group of
> several trained professionals should be able to fare much better :)

Right but ia64 - for better or worse started off as a hideously
divergent tree that did really stupid things like redefine GFP_DMA. It
may be that ia64 should have aimed in a different direction from day one
but having finally ended up in the right place *is* a milestone.


  reply	other threads:[~2003-08-04 19:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04 17:37 David Mosberger
2003-08-04 17:53 ` H. J. Lu
2003-08-04 18:00   ` Jesse Barnes
2003-08-04 18:10     ` H. J. Lu
2003-08-04 18:52       ` Jesse Barnes
2003-08-04 19:18         ` Andreas Schwab
2003-08-04 18:27     ` David Mosberger
2003-08-04 18:49       ` Jesse Barnes
2003-08-04 18:21   ` David Mosberger
2003-08-04 18:41     ` Jes Sorensen
2003-08-04 18:31 ` David S. Miller
2003-08-04 18:40   ` David Mosberger
2003-08-04 18:45     ` David S. Miller
2003-08-04 19:07       ` Alan Cox [this message]
2003-08-04 19:17         ` David S. Miller
2003-08-04 23:06 ` Peter Chubb
2003-08-04 23:35   ` David Mosberger
2003-08-13  0:07     ` Ian Wienand
2003-09-10  0:53       ` Ian Wienand
2003-09-10  1:57         ` David Mosberger

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=1060024077.719.26.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®