From: Jes Sorensen <jes@sunsite.dk>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Samium Gromoff <_deepfire@mail.ru>, linux-kernel@vger.kernel.org
Subject: Re: Will 2.6 require Python for any configuration ? (CML2)
Date: 24 Aug 2001 14:59:37 +0200 [thread overview]
Message-ID: <d3ofp5wr46.fsf@lxplus035.cern.ch> (raw)
In-Reply-To: <E15a1rW-000MM9-00@f10.mail.ru> <20010823143443.F14302@cpe-24-221-152-185.az.sprintbbd.net>
In-Reply-To: Tom Rini's message of "Thu, 23 Aug 2001 14:34:43 -0700"
>>>>> "Tom" == Tom Rini <trini@kernel.crashing.org> writes:
Tom> On Fri, Aug 24, 2001 at 01:18:02AM +0400, Samium Gromoff wrote:
>> but imagine the X arch hacker does not like python, and
>> nevertheless needs to port it on arch X. still fun?
Tom> Well I know python is endian-clean. I'd suspect it's even
Tom> 32/64bit clean. So it's not a matter of 'port' but compile. And
Tom> Linus has done things which have made lots of kernel hackers
Tom> scratch their head for a while. (Jump out of this fire and into
Tom> the min/max macros in 2.4.9 fire to see what I mean).
Again, please try and do real porting work before you make such silly
statements. Perl is 32/64 little/big-endian clean ... and still it's
the absolutely worst app to bring up (even X tends to be easier).
There is a lot more to this than meets the eye!
Jes
next prev parent reply other threads:[~2001-08-24 13:00 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 21:18 Will 2.6 require Python for any configuration ? (CML2) Samium Gromoff
2001-08-23 21:34 ` Tom Rini
2001-08-24 12:59 ` Jes Sorensen [this message]
2001-08-24 15:37 ` Tom Rini
2001-08-24 15:42 ` Jes Sorensen
2001-08-24 15:50 ` Tom Rini
2001-08-24 16:03 ` Jes Sorensen
[not found] <20010823191423.I14302@cpe-24-221-152-185.az.sprintbbd.net>
2001-08-24 3:01 ` Rick Hohensee
-- strict thread matches above, loose matches on Subject: below --
2001-08-23 21:39 Samium Gromoff
2001-08-23 21:12 Samium Gromoff
2001-08-23 21:32 ` Tom Rini
2001-08-23 21:08 Rick Hohensee
2001-08-23 21:01 ` Tom Rini
2001-08-23 20:56 Samium Gromoff
2001-08-23 21:14 ` Tom Rini
2001-08-23 20:41 Samium Gromoff
2001-08-23 20:53 ` Tom Rini
2001-08-25 4:11 ` Ben Ford
2001-08-25 14:51 ` Tom Rini
2001-08-22 6:08 =?unknown-8bit?B?RnLpZOlyaWMgTC4gVy4=?= Meunier
2001-08-23 12:05 ` Roland Bauerschmidt
2001-08-23 15:36 ` Bob Glamm
2001-08-23 15:55 ` Disconnect
2001-08-23 18:36 ` Daniel Phillips
2001-08-23 18:44 ` Disconnect
2001-08-23 19:01 ` David Weinehall
2001-08-23 19:22 ` Alan Cox
2001-08-23 19:02 ` Roland Bauerschmidt
2001-08-23 19:09 ` Rik van Riel
2001-08-23 19:31 ` Disconnect
2001-08-23 22:52 ` John Alvord
2001-08-24 1:51 ` Keith Owens
2001-08-23 15:55 ` Joshua Schmidlkofer
2001-08-23 15:59 ` Tom Rini
2001-08-23 19:26 ` Jes Sorensen
2001-08-23 19:32 ` David Weinehall
2001-08-23 19:41 ` Tom Rini
2001-08-23 19:50 ` Tom Rini
2001-08-23 20:02 ` Jes Sorensen
2001-08-23 20:13 ` Tom Rini
2001-08-23 20:43 ` Jes Sorensen
2001-08-23 21:12 ` Tom Rini
2001-08-24 4:59 ` Denis Perchine
2001-08-24 6:35 ` Leonid Mamtchenkov
2001-08-24 7:13 ` Denis Perchine
2001-08-24 15:01 ` Mark Hahn
2001-08-24 13:35 ` Ryan W. Maple
2001-08-25 1:14 ` Michael Peddemors
2001-08-24 17:42 ` David Lang
2001-08-23 16:24 ` Roland Bauerschmidt
2001-08-23 17:57 ` Kurt Roeckx
2001-08-24 8:10 ` Matthias Andree
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=d3ofp5wr46.fsf@lxplus035.cern.ch \
--to=jes@sunsite.dk \
--cc=_deepfire@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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