From: Randolph Chung <randolph@tausq.org>
To: Sir Ace <chandler@nateng.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Kernel 2.4.20 help?
Date: Wed, 22 Jan 2003 17:30:58 -0800 [thread overview]
Message-ID: <20030123013058.GD11363@tausq.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0301221718210.21999-100000@jordan.eng.nateng.com>
In reference to a message from Sir Ace, dated Jan 22:
>
> I've been playing with the 2.4.20 on my box {debian 3.0 parisc}
> I've found a few problems, tried a couple of fixes and got chewed out by a
> kernel deveolper so I saw you mentioned on the debian site and thought I
> should ask you.
where did you get your kernel tree? you need to use a tree downloaded
from parisc-linux.org, instead of an "official" linux tree,
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2003-01-23 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 1:19 [parisc-linux] Kernel 2.4.20 help? Sir Ace
2003-01-23 1:30 ` Randolph Chung [this message]
2003-01-23 1:44 ` Sir Ace
2003-01-23 2:47 ` Randolph Chung
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=20030123013058.GD11363@tausq.org \
--to=randolph@tausq.org \
--cc=chandler@nateng.com \
--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