From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: vester.thacker@gmail.com, 9fans@cse.psu.edu
Subject: Re: [9fans] Creating new documents on KFS, Fossil,
Date: Sun, 26 Sep 2004 02:02:29 -0600 [thread overview]
Message-ID: <4bc1f50b5b6bea002d7a3d89cd287db4@plan9.ucalgary.ca> (raw)
In-Reply-To: <32a656c204092600075a443a7d@mail.gmail.com>
> 2. I know many of the Plan 9 papers are clearly outdated
the problem you're going to run into is, strictly academically
speaking, that you won't be able to modify any of the documentation
without publishing the modifications. if you want to have an
up-to-date venti description you should publish an up-to-date venti
paper.
publishing is much more difficult than writing man pages, so it's not
a surprise that you see a fossil paper still lingering in the
documentation corners without having an official release with a
conference-backed citation, just look at
http://plan9.bell-labs.com/sys/doc/fossil.ps
two paths lead to a solution to this problem. either write
documentation accessible to anyone everywhere (i.e. man pages) or
leave others to ponder on implementation solutions through the papers.
the second one has an obvious drawback -- on a frequently used system
it won't matter how much you change the papers, the implementation is
always going to be one step ahead.
andrey
next prev parent reply other threads:[~2004-09-26 8:02 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 ` andrey mirtchovski [this message]
2004-09-26 8:37 ` [9fans] Creating new documents on KFS, Fossil, geoff
2004-09-27 2:08 ` Kenji Okamoto
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=4bc1f50b5b6bea002d7a3d89cd287db4@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--cc=9fans@cse.psu.edu \
--cc=vester.thacker@gmail.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;
as well as URLs for NNTP newsgroup(s).