From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kl
Date: Tue, 2 Apr 2002 12:32:10 +0200 [thread overview]
Message-ID: <20020402123209.U6290@cackle.proxima.alt.za> (raw)
In-Reply-To: <20020402094046.1B00219988@mail.cse.psu.edu>; from forsyth@caldo.demon.co.uk on Tue, Apr 02, 2002 at 10:37:12AM +0100
On Tue, Apr 02, 2002 at 10:37:12AM +0100, forsyth@caldo.demon.co.uk wrote:
>
> i think this is at least part of the problem (kl isn't up to date in
> the released version, and hasn't got the xrefresolv changes).
> it links cpu when i include them. i suppose there was a backwards
> dependency somewhere.
>
Validated.
I'm trying to build a "stable" system based on the March 27, 2001
distribution plus the few minor updates that followed. That much
I have no trouble with.
More difficult is going through the mail since October 2001 and
picking all the little nits that have appeared on this list. Maybe
in vain, I'd like to ask if anyone has actually tracked these
separately and can either point me to them or forward them to me.
Also, it may be asking a bit much, but perhaps we can add a short
recognisable keyword on the subject header when a patch is involved.
It would also help if one then stayed on topic <blush>.
++L
prev parent reply other threads:[~2002-04-02 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 9:37 forsyth
2002-04-02 10:32 ` Lucio De Re [this message]
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=20020402123209.U6290@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).