From: willy@thepuffingroup.com
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] updated web site
Date: Mon, 14 Feb 2000 23:22:16 -0500 [thread overview]
Message-ID: <20000214232216.S9944@thepuffingroup.com> (raw)
I've updated the website: http://www.thepuffingroup.com/parisc/
Please let me know of any inaccuracies. Of particular note is the
status page which has an up-to-date jobs list. Anything which doesn't
have someone's name next to it is an unclaimed project. Mail me to
volunteer (or to suggest other projects that I've missed).
We have a randomised-config-builder running here and I get the results.
Almost all of the configurations don't build :-) If we set up a list
that the results were mailed to, would anyone be interested in subscribing
to it and fixing some of the breakages? It's quite high-traffic; about
30k every hour -- depending how far the build gets before failing.
reply other threads:[~2000-02-15 5:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20000214232216.S9944@thepuffingroup.com \
--to=willy@thepuffingroup.com \
--cc=parisc-linux@thepuffingroup.com \
/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