From: Matthew Wilcox <matthew@wil.cx>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] I am not your mother!
Date: Sat, 30 Sep 2000 20:02:18 +0100 [thread overview]
Message-ID: <20000930200218.A25304@parcelfarce.linux.theplanet.co.uk> (raw)
I'd really appreciate it if people would update the website when they
make changes to how something works that will be user visible. It's not
hard; just cvs co website, make your corrections, and cvs ci.
My thanks to the people who _do_ do this already, including grant,
dhd and paul (keeping the status page up to date is rather important!).
Is there anything which can be done to make updating the website easier?
I've done my best to make it logical and easy; including getting rid
of the unusual build tool we were using and reducing the dependencies
involved in getting the page datestamp correct. There's nothing _hard_
to do, if you know enough to write code and check it in, you can handle
the website. So what's stopping you?
--
Revolutions do not require corporate support.
next reply other threads:[~2000-09-30 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-30 19:02 Matthew Wilcox [this message]
2000-10-02 14:17 ` [parisc-linux] I am not your mother! David Huggins-Daines
2000-10-02 14:26 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2000-10-03 1:17 MEYER,ALAN C. (HP-FtCollins,ex1)
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=20000930200218.A25304@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--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