From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Machine-specific cpurc customisation?
Date: Wed, 15 Oct 2003 11:13:23 +0100 [thread overview]
Message-ID: <94150691419a95546ac0d4bd0e2dbc61@caldo.demon.co.uk> (raw)
In-Reply-To: <1a00bd74118a0aacdc816bb3158aa117@plan9.escet.urjc.es>
i use a case on sysname in cpurc and compare updates on sources as they rarely occur.
i find it's easier to have everything in one file not scattered across
several. (the largest cpurc i've used had 13 cases with 5 architectures.)
default case * gives a `normal' general-purpose cpu server.
prev parent reply other threads:[~2003-10-15 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 7:14 Adrian Tritschler
2003-10-15 9:51 ` Fco.J.Ballesteros
2003-10-15 10:13 ` Charles Forsyth [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=94150691419a95546ac0d4bd0e2dbc61@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).