From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] six-ty seven ^fprints on the wall, six-ty seven ^fprints
Date: Sun, 12 Oct 2003 10:57:33 -0400 [thread overview]
Message-ID: <E1A8hf4-0000Op-D8@t40.swtch.com> (raw)
I really think you want a lot of those fprints.
Perhaps instead of removing them they should be
fixed up to give more context and thus make sense
to more people.
If you remove, for example, the fprints in drawterm
or in vac, when disaster strikes it will just sit
there rather than tell you what happened. I'd rather
have it talk to me.
Russ
next reply other threads:[~2003-10-12 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 14:57 Russ Cox [this message]
2003-10-12 15:39 ` David Presotto
2003-10-12 17:15 ` matt
2003-10-12 18:24 ` Jim Choate
-- strict thread matches above, loose matches on Subject: below --
2003-10-12 12:17 matt
2003-10-12 12:40 ` David Presotto
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=E1A8hf4-0000Op-D8@t40.swtch.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).