From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] [plan9port] graphics
Date: Wed, 28 Jun 2006 14:42:42 -0700 [thread overview]
Message-ID: <ee9e417a0606281442o47c99a44o2bab54f1f86ef68c@mail.gmail.com> (raw)
In-Reply-To: <6e35c0620606281413q233ec707hef9dcc32d22f4508@mail.gmail.com>
> Just out of curiosity, have you seen any noticeable difference in
> performance, good or bad?
No. Except my own performance, since I don't have to restart
my 9term windows and my acme multiple times per day anymore.
Russ
next prev parent reply other threads:[~2006-06-28 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 17:46 Russ Cox
2006-06-28 21:13 ` Jack Johnson
2006-06-28 21:42 ` Russ Cox [this message]
2006-06-29 2:04 ` Roman Shaposhnick
2006-06-29 3:59 ` David Leimbach
2006-06-29 4:27 ` quanstro
2006-06-29 15:36 ` Russ Cox
2006-06-29 18:59 ` Roman Shaposhnick
2006-07-12 15:36 ` andrey mirtchovski
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=ee9e417a0606281442o47c99a44o2bab54f1f86ef68c@mail.gmail.com \
--to=rsc@swtch.com \
--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).