mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	Martin Orr <martin@martinorr.name>,
	Stefano Rivoir <s.rivoir@gts.it>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.22 released
Date: Wed, 11 Jul 2007 19:56:34 -0400	[thread overview]
Message-ID: <20070711235634.GK4887@tamriel.snowman.net> (raw)
In-Reply-To: <alpine.LFD.0.999.0707111534340.20061@woody.linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

* Linus Torvalds (torvalds@linux-foundation.org) wrote:
> But yeah, if Debian/sid is just using random compiler snapshots of the 
> day, I htink we can just bury this as "pointless".

Err, debian/sid *isn't* defaulting to gcc-4.2 yet, but it is made
available to people who want to install it and play with it.

Additionally, the kernel build is actually tied to a specific compiler
(doesn't default to just using whatever the default compiler is) so even
when gcc-4.2 is eventually made the default compiler the linux images
built for Debian won't use it immediately.  That change will be made
seperately and after additional testing to make sure it doesn't break
the built kernel which is distributed.

	Thanks,

		Stephen

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-07-12  0:09 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 23:52 Linus Torvalds
2007-07-09  0:19 ` Jesper Juhl
2007-07-09  1:08 ` Phil Oester
2007-07-09  6:06   ` Jan De Luyck
2007-07-09  5:00 ` Willy Tarreau
2007-07-09 10:14 ` Alan Cox
2007-07-10 18:41   ` Chuck Ebbert
2007-07-09 10:30 ` Jan Engelhardt
2007-07-09 11:45   ` Jan Engelhardt
2007-07-09 14:25 ` Michal Piotrowski
2007-07-10  7:17 ` Stefano Rivoir
2007-07-10  8:52   ` Andrew Morton
2007-07-10 15:39   ` Linus Torvalds
2007-07-10 15:59     ` Stefan Richter
2007-07-11  6:38     ` Stefano Rivoir
2007-07-11  7:05       ` Linus Torvalds
2007-07-11 10:55         ` Stephen Frost
2007-07-11 14:28           ` Stefano Rivoir
2007-07-11 12:35       ` Martin Orr
2007-07-11 14:27         ` Stefano Rivoir
2007-07-11 13:10       ` Andi Kleen
2007-07-11 17:51         ` Martin Orr
2007-07-11 18:01           ` Linus Torvalds
2007-07-11 21:00             ` Martin Orr
2007-07-11 21:29               ` Linus Torvalds
2007-07-11 22:16                 ` Andi Kleen
2007-07-11 22:33                   ` Serge Belyshev
2007-07-11 22:37                   ` Linus Torvalds
2007-07-11 22:43                     ` Andi Kleen
2007-07-11 23:56                     ` Stephen Frost [this message]
2007-07-14 15:48                   ` Martin Orr
2007-07-11 16:25       ` Theodore Tso
2007-07-10 19:39 ` Valdis.Kletnieks
2007-07-10 22:26   ` Adrian Bunk
2007-07-10 23:12     ` Stefan Richter
2007-07-11  0:00       ` Adrian Bunk
2007-07-11 10:57         ` Stefan Richter
2007-07-11  0:32       ` Valdis.Kletnieks
2007-07-11  0:01     ` david

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=20070711235634.GK4887@tamriel.snowman.net \
    --to=sfrost@snowman.net \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@martinorr.name \
    --cc=s.rivoir@gts.it \
    --cc=torvalds@linux-foundation.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

Powered by JetHome