From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] 9front Programmer's Manual
Date: Fri, 06 Aug 2021 11:05:30 -0400 [thread overview]
Message-ID: <18BDAB449FBB20989093FC284E3A89F1@eigenstate.org> (raw)
In-Reply-To: <YQ0mSRCblZvISAnb@beryllium.local>
Quoth Humm <hummsmith42@gmail.com>:
>
> So, what’s the situation? Are there any plans other than continuing
> to let it rot?
Updates and fixes to manpages are always
welcome and applied regularly. Improving
and fixing the build system is also good.
But papers are papers. It seems strange
to modify them. I think for papers, it
makes most sense to add a 'changes since
publication' document.
I'd also like more tutorial or 'theory of
operation' style docs that supplement the
manpages, and show how parts of the system
fit together, but I'm not much of a writer,
and haven't put much thought into this.
next prev parent reply other threads:[~2021-08-06 22:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 12:08 Humm
2021-08-06 13:37 ` qwx
2021-08-06 15:00 ` Humm
2021-08-06 13:49 ` qwx
2021-08-06 15:05 ` ori [this message]
2021-08-06 19:30 ` Stuart Morrow
2021-08-07 4:52 ` sirjofri
2021-08-20 11:26 ` Stuart Morrow
2021-08-06 15:06 ` Stanley Lieber
2021-08-06 19:34 ` Stuart Morrow
2021-08-07 11:37 ` Humm
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=18BDAB449FBB20989093FC284E3A89F1@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/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).