From: Anthony Fok <foka@debian.org>
To: Anton Blanchard <anton@linuxcare.com.au>
Cc: "ASN Stevens, Computing Service" <Alastair.Stevens@bristol.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.1-ac12 compile failure on sparc64
Date: Wed, 14 Feb 2001 11:23:04 -0700 [thread overview]
Message-ID: <20010214112304.C22741@lovelife.olvc.ab.ca> (raw)
In-Reply-To: <EXECMAIL.1010214113238.Y@velifer.bris.ac.uk> <20010214224148.C2132@linuxcare.com>
In-Reply-To: <20010214224148.C2132@linuxcare.com>; from anton@linuxcare.com.au on Wed, Feb 14, 2001 at 10:41:48PM +1100
On Wed, Feb 14, 2001 at 10:41:48PM +1100, Anton Blanchard wrote:
> > Hi - I am having compilation troubles on my sparc64 workstation (standard
> > Ultra 5 machine), which is currently running stock 2.4.1 on Red Hat 6.2 quite
> > happily.
>
> We arent tracking the -ac patches at the moment and alan can't be expected
> to ensure it compiles on all architectures. Best bet is to stick with
> Linus releases.
You are right, of course, but then ASN Stephens is also right for reporting
a problem in the -ac patches. Or do you expect people to ignore bugs in the
-ac series and let bugs go unreported? How will the -ac series improve, and
ultimately, how will the official Linux kernel improve?
Granted, in this case, Alan already knew the problem. :-)
Cheers,
Anthony
--
Anthony Fok Tung-Ling Civil and Environmental Engineering
foka@ualberta.ca, foka@debian.org University of Alberta, Canada
Debian GNU/Linux Chinese Project -- http://www.debian.org/intl/zh/
Come visit Our Lady of Victory Camp -- http://www.olvc.ab.ca/
next prev parent reply other threads:[~2001-02-14 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 11:32 ASN Stevens, Computing Service
2001-02-14 11:41 ` Anton Blanchard
2001-02-14 17:54 ` Aaron Dewell
2001-02-14 18:23 ` Anthony Fok [this message]
2001-02-14 12:23 ` Alan Cox
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=20010214112304.C22741@lovelife.olvc.ab.ca \
--to=foka@debian.org \
--cc=Alastair.Stevens@bristol.ac.uk \
--cc=anton@linuxcare.com.au \
--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
all inboxes | Powered by JetHome®