public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Johan Kullstam" <kullstam@ne.mediaone.net>
To: linux-kernel@vger.kernel.org
Subject: Re: ReiserFS Oops (2.4.1, deterministic, symlink related)
Date: 02 Feb 2001 22:43:42 -0500	[thread overview]
Message-ID: <m2hf2ce8i9.fsf@euler.axel.nom> (raw)
In-Reply-To: <Pine.LNX.4.30.0102021438320.9097-100000@age.cs.columbia.edu>
In-Reply-To: <Pine.LNX.4.30.0102021438320.9097-100000@age.cs.columbia.edu>

Ion Badulescu <ionut@cs.columbia.edu> writes:

> On Fri, 2 Feb 2001, Alan Cox wrote:
> 
> > Oh I can see why Hans wants to cut down his bug reporting load. I can also
> > say from experience it wont work. If you put #error in then everyone will
> > mail him and complain it doesnt build, if you put #warning in nobody will
> > read it and if you dont put anything in you get the odd bug report anyway.
> >
> > Basically you can't win and unfortunately a shrink wrap forcing the user
> > to read the README file for the kernel violates the GPL ..
> 
> Oh, don't get me wrong, I fully understand that it's a lose-lose
> situation. All I'm saying is that it was an incredibly bad idea to have
> two compilers, one broken and one ok, identify themselves as the same
> version.

unfortunately, it's not limited to redhat and it's not limited to
redhat's gcc-2.96.  gcc-2.95.2 has some bugs (a certain strength
reduction bug comes to mind).  no new official gcc has come for over a
year.  many distributions have applied a patch to fix the strength
reduction bug.  do they all alter their version number?  of those that
do, do they alter it consistently?

-- 
J o h a n  K u l l s t a m
[kullstam@ne.mediaone.net]
Don't Fear the Penguin!
-
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/

  reply	other threads:[~2001-02-03  3:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cs.lists.linux-kernel/E14OjME-0006nU-00@the-village.bc.nu>
2001-02-02 21:22 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Ion Badulescu
2001-02-02 21:57   ` Alan Cox
2001-02-02 22:06     ` Arthur Erhardt
2001-02-02 22:06     ` Hans Reiser
2001-02-02 22:57       ` Ion Badulescu
2001-02-05  2:50       ` Brian Wolfe
2001-02-05  4:08         ` Albert D. Cahalan
2001-02-05 11:58           ` Alan Cox
2001-02-05 11:36             ` Hans Reiser
2001-02-05 12:44               ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Alan Cox
2001-02-05 12:16                 ` Hans Reiser
2001-02-05 12:52                   ` Alan Cox
2001-02-05 12:33                     ` Hans Reiser
2001-02-05 12:57                   ` Dr. David Gilbert
2001-02-05 16:57               ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) James Sutherland
2001-02-12  3:41               ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Albert D. Cahalan
2001-02-12  9:45                 ` Hans Reiser
2001-02-05 12:16             ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Dr. David Gilbert
2001-02-05  5:21         ` Gregory Maxwell
2001-02-05 12:02           ` Alan Cox
2001-02-05 11:38             ` Hans Reiser
2001-02-05 11:55         ` Alan Cox
2001-02-05 11:35           ` Hans Reiser
2001-02-05 20:19           ` Brian Wolfe
2001-02-02 22:42     ` Ion Badulescu
2001-02-03  3:43       ` Johan Kullstam [this message]
2001-02-03  8:57     ` David Ford
2001-02-03 10:00       ` J . A . Magallon
2001-02-03 23:26         ` Felix von Leitner
2001-02-04 11:04           ` Alan Cox
2001-02-04  3:24       ` John Alvord
2001-02-02 11:28 Jan Kasprzak

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=m2hf2ce8i9.fsf@euler.axel.nom \
    --to=kullstam@ne.mediaone.net \
    --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