From: erik quanstrom <quanstro@quanstro.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Understanding /dev/draw
Date: Thu, 18 Apr 2019 10:52:05 -0700 [thread overview]
Message-ID: <cb49ebf3-e1cc-4342-a752-d8a1d479b673@email.android.com> (raw)
In-Reply-To: <CAJSxfmK0Kgb0FZo+kQAh6x-=dNeahQG0ido+oQ=XpsbQ83G=WQ@mail.gmail.com>
[-- Attachment #1: Type: text/html, Size: 3300 bytes --]
next prev parent reply other threads:[~2019-04-18 17:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 14:35 Chris McGee
2019-04-18 15:01 ` Lucio De Re
2019-04-18 15:25 ` Skip Tavakkolian
2019-04-18 15:30 ` Skip Tavakkolian
2019-04-18 15:33 ` Chris McGee
2019-04-18 17:27 ` Skip Tavakkolian
2019-04-18 17:52 ` erik quanstrom [this message]
2019-04-18 19:03 ` Chris McGee
2019-04-18 19:30 ` Joseph Stewart
2019-04-18 20:40 ` Skip Tavakkolian
2019-04-18 22:28 ` Joseph Stewart
2019-04-18 22:33 ` hiro
2019-04-18 19:33 ` erik quanstrom
2019-04-18 20:37 ` David Hoskin
2019-04-19 0:22 ` Chris McGee
2019-04-19 1:26 ` David Hoskin
2019-04-18 18:12 ` hiro
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=cb49ebf3-e1cc-4342-a752-d8a1d479b673@email.android.com \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).