From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: Tr: [9fans] off topic: troff book
Date: Fri, 19 Jan 2001 14:02:16 +0000 [thread overview]
Message-ID: <3A684738.8010708@null.net> (raw)
In-Reply-To: <001901c08107$aa6d0700$0ab9c6d4@cybercable.fr>
Boyd Roberts wrote:
> are we writing code or comments?
Well, if you're writing *maintainable* code,
you're including appropriate comments.
next prev parent reply other threads:[~2001-01-19 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 15:24 Russ Cox
2001-01-18 4:32 ` Boyd Roberts
2001-01-19 14:02 ` Douglas A. Gwyn [this message]
2001-01-19 14:23 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-01-16 19:12 Scott Schwartz
2001-01-16 19:13 ` Boyd Roberts
2001-01-16 18:05 Boyd Roberts
2001-01-17 9:35 ` saroj
2001-01-17 12:12 ` Boyd Roberts
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=3A684738.8010708@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).