9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ddc
Date: Wed,  6 Nov 2002 16:44:52 -0500	[thread overview]
Message-ID: <d66f6106c3f5868484f33cb569520f86@plan9.bell-labs.com> (raw)

Perhaps a more accurate response would have been:

	I have no plan, and to the best of my knowledge jmk
	has no plan, and since we're the two who have hacked
	on vga the most in recent years, you might well conclude
	that no one has any likely-to-be-executed plan to add
	DDC suport in the near future.

Saying things like that strikes me as overly pedantic, when
it should be taken as a given that I'm not speaking for any
collections of users anyway.

> Sigh, shouldn't the -user community- be making this decision...

The only decision I see in the post is about my deciding it wasn't
worth my time to work on vga further.  And I would argue that
I, not the -user community-, have every right to make decisions
about how I spend my time.

There's no policy anywhere.  The only decisions are about what
you do with your own time.  If you want to write or change
something, all the source is there.  Have at it.

> I can say that there is a significant contingent of Hangar 18 users
> who disagree with the assertion that the current VGA support is
> good enough.

That's fine.  Please, go ahead.  I would be more than happy
if the user community wrote more tools and did things like
this.  (Some have, and I am quite grateful.)  I agree that the
VGA support isn't good enough for many applications, but
_for me_, those applications aren't important enough to warrant
spending more time on vga.

Russ



             reply	other threads:[~2002-11-06 21:44 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 21:44 Russ Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-07 20:34 presotto
2002-11-07 19:03 presotto
2002-11-07 19:55 ` Jack Johnson
2002-11-07 18:58 Joel Salomon
2002-11-07 19:20 ` Dan Cross
2002-11-07 18:05 Russ Cox
2002-11-07 18:11 ` Jim Choate
2002-11-07 16:35 Russ Cox
2002-11-07 18:00 ` Jim Choate
2002-11-07 16:28 Skip Tavakkolian
2002-11-07 10:59 nigel
2002-11-07 13:48 ` Jim Choate
2002-11-07 14:21   ` Jim Choate
2002-11-07 18:35   ` Dan Cross
2002-11-07 18:53     ` Jim Choate
2002-11-07 18:58       ` Dan Cross
2002-11-07  5:51 Scott Schwartz
2002-11-07  6:09 ` Jim Choate
2002-11-06 23:27 Russ Cox
2002-11-06 23:31 ` Jim Choate
2002-11-07  0:13   ` nojkwspm
2002-11-06 22:06 nigel
2002-11-06 23:23 ` Jim Choate
2002-11-06 18:10 Russ Cox
2002-11-06 20:41 ` Jim Choate
2002-11-06 17:37 Russ Cox
2002-11-06 17:50 ` andrey mirtchovski
2002-11-06 19:33   ` Scott Schwartz
2002-11-06 20:39 ` Jim Choate
2002-11-07  3:17   ` Doc Shipley
2002-11-07  4:57     ` Jim Choate
2002-11-07  5:39       ` Lucio De Re
2002-11-07  5:45       ` Doc Shipley
2002-11-07  6:08         ` Jim Choate
2002-11-07  4:21 ` Lucio De Re
2002-11-07  8:24 ` paurea
2002-11-06 17:25 paurea

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=d66f6106c3f5868484f33cb569520f86@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.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).