From: Benedict Bridgwater <bennyb@ntplx.net>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Brown-paper-bag bug in m68k, sparc, and sparc64 config files
Date: Sat, 19 May 2001 21:06:51 -0400 [thread overview]
Message-ID: <3B0718AB.7E2FF3A2@ntplx.net> (raw)
> This bug unconditionally disables a configuration question -- and it's
> so old that it has propagated across three port files, without either
> of the people who did the cut and paste for the latter two noticing it.
>
> This sort of thing would never ship in CML2, because the compiler
> would throw an undefined-symbol warning on BLK_DEV_ST. The temptation
> to engage in sarcastic commentary at the expense of people who still
> think CML2 is an unnecessary pain in the butt is great. But I will
> restrain myself. This time.
So a shortcoming of the CML1 tools justifies the CML2 language?
I guess the next bug found in the Python2 interpreter will justify
writing CML3 in FORTRAN.
Ben
next reply other threads:[~2001-05-20 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-20 1:06 Benedict Bridgwater [this message]
2001-05-20 1:51 ` Brown-paper-bag bug in m68k, sparc, and sparc64 config files Miles Lane
2001-05-20 2:14 ` Ben Bridgwater
2001-05-20 3:14 ` Keith Owens
2001-05-20 1:51 ` Miles Lane
-- strict thread matches above, loose matches on Subject: below --
2001-05-19 22:10 Eric S. Raymond
2001-05-20 4:10 ` Mike Galbraith
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=3B0718AB.7E2FF3A2@ntplx.net \
--to=bennyb@ntplx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.