linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.75
Date: Thu, 10 Jul 2003 15:26:09 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0307101512350.4757-100000@home.osdl.org> (raw)
In-Reply-To: <20030710223548.A20214@flint.arm.linux.org.uk>


On Thu, 10 Jul 2003, Russell King wrote:
> 
> Well, only two words from me.  Oh Shit.

Hey, this is already much later than it should have been, so it's not as
if this is a huge surprise.

> The 2.5.70 ARM patch currently looks like this:

We can sort it out later. Obviously, clearly arm-specific patches (ie
stuff in arch/arm and include/asm-arm) I wouldn't mind per se, but I'd
rather hold back on even those just to make the patches and the changlogs
not be mixed up with the "main bugfixes".

We've never had a first stable release that has all architectures
up-to-date, and I'm not planning on changing that for 2.6.x. This is _not_
the time to try to make my tree build on arm (or other architectures
either), considering that my tree hasn't been the main ARM tree for a long 
time.

> Frustrated such an understatement.

To be blunt, which part of "we want to release 2.6.x this year" came as a
surprise to you? I

That means that I'm not willing to hold stuff up any more. Stuff that 
hasn't followed the development tree doesn't magically just "get fixed". 

Also, the only real point of a stable release is for distribution makers.
That pretty much cuts the list of "needs to be supported" down to x86,
ia64, x86-64 and possibly sparc/alpha.

So everything else is a bonus, but can equally well just play catch-up
later. Embedded people tend to want to stay back anyway, which is 
obviously why they don't follow the development tree in the first place. 

			Linus


  reply	other threads:[~2003-07-10 22:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10 21:14 Linux 2.5.75 Linus Torvalds
2003-07-10 21:35 ` Russell King
2003-07-10 22:26   ` Linus Torvalds [this message]
2003-07-10 23:05     ` Russell King
2003-07-10 23:25       ` Linus Torvalds
2003-07-11 19:59       ` Horst von Brand
2003-07-10 23:30 ` Felipe Alfaro Solana
2003-07-10 23:38   ` Linus Torvalds
2003-07-10 23:46     ` Davide Libenzi
2003-07-10 23:40   ` Robert Love
2003-07-11  0:24     ` Diego Calleja García
2003-07-11  0:49       ` Wade
2003-07-11  7:09 ` Benjamin Herrenschmidt
2003-07-11 10:57 ` Linux 2.5.75 - still can't load aha152x (isapnp) => OOPS schmurtz
2003-07-11 17:53   ` Andrew Morton
2003-07-11 18:04     ` James Bottomley
2003-07-11 18:45     ` schmurtz
2003-07-11 12:30 ` incbin (was: Re: Linux 2.5.75) Geert Uytterhoeven
2003-07-11 12:32   ` Geert Uytterhoeven
2003-07-11 15:46 ` Linux 2.5.75 Oliver Pitzeier
2003-07-11 15:52 ` Linux 2.5.75 (compile statistics) John Cherry
2003-07-12 13:50 ` AMD 53C974 based SCSI adapter (was: Linux 2.5.75) Matthias Andree
     [not found] <20030710223548.A20214@flint.arm.linux.org.uk.suse.lists.linux.kernel>
     [not found] ` <Pine.LNX.4.44.0307101512350.4757-100000@home.osdl.org.suse.lists.linux.kernel>
2003-07-10 23:55   ` Linux 2.5.75 Andi Kleen
2003-07-11  0:12     ` Linus Torvalds
2003-07-11  0:55       ` Paul Mackerras
2003-07-11  8:42       ` Christoph Hellwig
2003-07-11 10:27         ` Lars Marowsky-Bree
2003-07-11 10:39           ` Christoph Hellwig
2003-07-11 16:52           ` Linus Torvalds
2003-07-11 17:03             ` Arjan van de Ven
2003-07-12 19:20               ` Horst von Brand
2003-07-12 23:17                 ` Jeff Garzik
     [not found] <7TEe.Bz.21@gated-at.bofh.it>
     [not found] ` <7TNS.Kc.9@gated-at.bofh.it>
2003-07-11 21:33   ` Arnd Bergmann

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=Pine.LNX.4.44.0307101512350.4757-100000@home.osdl.org \
    --to=torvalds@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).