Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Michael S.Zick <mszick@goquest.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>, jsoe0708@tiscali.be
Cc: grundler@dsl2.external.hp.com, joel.soete@freebel.net,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] jfs-1.0.23 as well xfs-cvs break fb console on k-2.4.19-pa22
Date: Tue, 22 Oct 2002 10:02:17 -0500	[thread overview]
Message-ID: <02102210021702.00736@localhost.localdomain> (raw)
In-Reply-To: <200210211646.g9LGki9b016805@hiauly1.hia.nrc.ca>

On Monday 21 October 2002 11:46 am, John David Anglin wrote:
> > it sounds like a gcc bug:
>
> What does a gcc bug sound like ;-)
>
> Dave
It is an indirect call (Telepathic) -
You have to listen for its echo from the programmer's mouth.
Mike

  reply	other threads:[~2002-10-22 15:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17 17:48 [parisc-linux] FW: [Bug #3332] jfs-1.0.22 and 1.0.23 break fb console on k-2.4.19-pa22 jsoe0708
2002-10-18 14:43 ` jsoe0708
2002-10-18 14:07   ` [parisc-linux] Linux version 2.4.19-pa22 uname -a fault phi
2002-10-18 15:41     ` Thibaut VARENE
2002-10-18 15:57       ` Randolph Chung
2002-10-18 17:02   ` [parisc-linux] jfs-1.0.22 and 1.0.23 break fb console on k-2.4.19-pa22 jsoe0708
2002-10-19 19:45     ` [parisc-linux] jfs-1.0.23 as well xfs-cvs " Joel Soete
2002-10-20  3:44       ` Grant Grundler
2002-10-21 14:43         ` jsoe0708
2002-10-21 16:42           ` Randolph Chung
2002-10-21 17:48             ` jsoe0708
2002-10-21 16:46           ` John David Anglin
2002-10-22 15:02             ` Michael S.Zick [this message]
2002-10-22 15:36               ` John David Anglin
2002-10-23  5:54                 ` jsoe0708
2002-10-23 15:01                   ` John David Anglin
2002-10-24  5:44                     ` jsoe0708
2002-10-24 16:23                       ` John David Anglin

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=02102210021702.00736@localhost.localdomain \
    --to=mszick@goquest.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=grundler@dsl2.external.hp.com \
    --cc=joel.soete@freebel.net \
    --cc=jsoe0708@tiscali.be \
    --cc=parisc-linux@lists.parisc-linux.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