From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Pico (again)
Date: Mon, 29 Jul 2002 15:57:45 +0000 [thread overview]
Message-ID: <3D36FE1C.50676A22@null.net> (raw)
In-Reply-To: <20020718141436.3434B19A3E@mail.cse.psu.edu>
anothy@cosym.net wrote:
> anyone got anything to deal with pico (v10 picfile(5)) images?
Somewhere in my archives I have 5620/630 code.
IIRC, it is a simple format similar to .BMP and so it
should be easy to reformat it into any frame-buffer device.
next prev parent reply other threads:[~2002-07-29 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 14:14 anothy
2002-07-18 18:07 ` Fariborz (Skip) Tavakkolian
2002-07-18 23:07 ` Micah Stetson
2002-07-29 15:57 ` Douglas A. Gwyn [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-26 6:03 Byron Rakitzis
2002-07-18 20:04 Dennis Ritchie
2002-07-19 8:19 ` ggm
2002-07-29 15:57 ` Douglas A. Gwyn
2002-07-18 8:53 steve.simon
2002-07-17 22:46 Sam
2002-07-18 0:28 ` Fariborz (Skip) Tavakkolian
2002-07-17 23:19 ` Sam
2002-07-18 0:35 ` Fariborz (Skip) Tavakkolian
2002-07-18 9:51 ` William Josephson
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=3D36FE1C.50676A22@null.net \
--to=dagwyn@null.net \
--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).