From: Kenji Okamoto <okamoto@granite.cias.osakafu-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Creating new documents on KFS, Fossil,
Date: Mon, 27 Sep 2004 11:08:17 +0900 [thread overview]
Message-ID: <e86d4a3162307bce2a27086f66f3baf0@granite.cias.osakafu-u.ac.jp> (raw)
In-Reply-To: <769951127f98c1875fae89d5280aaf7d@collyer.net>
> There is a third possibility: the person who updates the code updates
> the corresponding paper, if any. This seems to be part of 1127's
> tradition that the person who writes the code writes the
> documentation.
I suppose this tradition can not be live long anymore bvecause of
dispersion of people, and they have their own job other than Plan 9
now.
The paper is paper, which makes us the things clearer than reading
so-called users manual. However, it'd be better if we have users
anual with papers for beginners. I'm not a person who can do it,
so, I'd be very happy if someone could use their time for that purpose.
If we have such, it's more easy to tell someone "Why you don't try
Plan 9?"
By the way, your updates to /sys/src/fs is very interesting to me.
All the sources are in sources?
> I should probably beat on fossil
> and see how robust it is these days.
Quite robust these days!
Kenji
next prev parent reply other threads:[~2004-09-27 2:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 7:07 [9fans] Creating new documents on KFS, Fossil, and Venti implementation and etc Vester Thacker
2004-09-26 7:50 ` Boris Maryshev
2004-09-26 8:06 ` Vester Thacker
2004-09-26 8:02 ` [9fans] Creating new documents on KFS, Fossil, andrey mirtchovski
2004-09-26 8:37 ` geoff
2004-09-27 2:08 ` Kenji Okamoto [this message]
2004-09-27 4:39 ` geoff
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=e86d4a3162307bce2a27086f66f3baf0@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).