From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] art(1) of the second release
Date: Tue, 7 Jan 2003 16:40:39 +0900 [thread overview]
Message-ID: <2a3fa3038722bd02a24327e3c472c496@granite.cias.osakafu-u.ac.jp> (raw)
I put the art(1) sources for Release 4 under the /n/sources/contrib/art
of sources.cs.bell-labs.com source server.
The art program was written by someone in the Bell Labs (I guess Tom
Duff, am I wrong?), and included in the second release of Plan 9 which
means it is protected by the license of that release. Therefore, I've been
putting only the diffs onto our web site for Release 3. This is partially
because I rewrote it for our students to learn how to write GUI programs
on Plan 9, yes, it is aimed for internally use. Now, I got the permission
to put them in the sources.cs.bell-labs.com.
As written above, it is not intended to heavy use, and it may have many
bugs in itself. If you'd like to inprove it, don't hesitate and do it by your
own. I'd be happy if I could have those improvements too.
Kenji
reply other threads:[~2003-01-07 7:40 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=2a3fa3038722bd02a24327e3c472c496@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).