From: Alan Cox <alan@redhat.com>
To: john@vmlinux.net (John Morrison)
Cc: reiser@namesys.com (Hans Reiser), alan@redhat.com (Alan Cox),
mason@suse.com (Chris Mason),
kas@informatics.muni.cz (Jan Kasprzak),
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
yura@yura.polnet.botik.ru (Yury Yu. Rupasov)
Subject: Re: [reiserfs-list] Re: ReiserFS Oops (2.4.1, deterministic, symlink
Date: Fri, 2 Feb 2001 16:39:18 -0500 (EST) [thread overview]
Message-ID: <200102022139.f12LdII21148@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0102022126300.883-100000@vaio.vmlinux.net> from "John Morrison" at Feb 02, 2001 09:34:12 PM
> It makes sense to refuse to build a piece of the kernel if it break's
> a machine - anything else is a timebomb waiting to explode.
The logical conclusion of that is to replace the entire kernel tree with
#error "compiler or program might have a bug. Aborting"
The kernel is NOT some US home appliance festooned with 'do not eat this
furniture' and 'do not expose your laserwrite to naked flame' messages.
The readme says its been tested with egcs-1.1.2 and gcc 2.95.
The same people who can't read documentation will just mail the list with
'it doesnt compile, help' or 'it doesnt compile, you suck' in less enlightened
cases/
Large numbers of people routinely build the kernel with 'unsupported' compilers
notably the pgcc project people and another group you will cause problems for
- the GCC maintainers. They use the kernel tree as part of the test set for
their kernel, something putting #ifdefs all over it will mean they have to
mess around to fix too.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-02 21:40 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 11:28 ReiserFS Oops (2.4.1, deterministic, symlink related) Jan Kasprzak
2001-02-02 11:04 ` [reiserfs-list] " Hans Reiser
2001-02-02 12:16 ` Jan Kasprzak
2001-02-02 12:34 ` Alan Cox
2001-02-02 13:09 ` Jan Kasprzak
2001-02-02 16:36 ` Jan Kasprzak
2001-02-02 16:46 ` Alan Cox
2001-02-02 12:26 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Alan Cox
2001-02-02 15:16 ` Chris Mason
2001-02-02 15:20 ` Alan Cox
2001-02-02 17:34 ` Hans Reiser
2001-02-02 18:25 ` Alan Cox
2001-02-02 20:43 ` Hans Reiser
2001-02-02 21:33 ` Alan Cox
2001-02-02 21:29 ` [reiserfs-list] " Hans Reiser
2001-02-02 22:13 ` Alan Cox
2001-02-02 22:13 ` Hans Reiser
2001-02-02 23:40 ` J . A . Magallon
2001-02-02 23:34 ` Hans Reiser
2001-02-03 0:17 ` Jakub Jelinek
2001-02-03 4:25 ` Paul Jakma
2001-02-03 7:58 ` Alan Cox
2001-02-03 9:18 ` J . A . Magallon
2001-02-03 9:48 ` Jakub Jelinek
2001-02-03 7:46 ` Alan Cox
2001-02-03 17:14 ` David Woodhouse
2001-02-03 17:33 ` Albert D. Cahalan
2001-02-03 17:56 ` Alan Cox
2001-02-03 23:49 ` Albert D. Cahalan
2001-02-02 21:34 ` John Morrison
2001-02-02 21:39 ` Alan Cox [this message]
2001-02-02 21:49 ` John Morrison
2001-02-02 22:03 ` Hans Reiser
2001-02-02 22:40 ` Alan Cox
2001-02-02 22:16 ` Hans Reiser
2001-02-02 22:58 ` alex
2001-02-03 0:40 ` Andre Pang
2001-02-03 2:22 ` James Sutherland
2001-02-02 22:52 ` Keith Owens
2001-02-09 9:39 ` Thomas Zehetbauer
2001-02-02 12:15 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) John Morrison
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=200102022139.f12LdII21148@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=john@vmlinux.net \
--cc=kas@informatics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=yura@yura.polnet.botik.ru \
/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